显示标签为“setup”的博文。显示所有博文
显示标签为“setup”的博文。显示所有博文

2012年3月29日星期四

Full text setup questions

My company has a web site that we bought several years ago, and we have had
to replace the machines that the site runs on. I have inherited the DBA role
for this system recently. The site search engine has not been working for
some time, and after digging through the asp code, I found this query:
sSql="SELECT a.article_id,srch.size,srch.rank "&_
"FROM OPENQUERY(FileSystem,"&_
"'SELECT FileName, Size,rank "&_
"FROM SCOPE('' """ & FormScope & """ '') "&_
"WHERE CONTAINS(Contents,''" & sSearch & "'') order by rank desc,write
desc') srch,articles a"
if NOT isCMS Then
sSql=sSql & ",columns c"
End If
sSql=sSql & " where cast(a.article_id as varchar(15))+'.htm'=srch.filename"
if NOT isCMS Then sSql=sSql & " AND a.status_id in (4,5) AND
c.column_id=a.column_id
So, after some searching, I discovered that this was using the Full-Text
Search function in SQL Server to search through the content news articles
under the wwwroot folder on the web server. What I'm having a hard time
doing now is creating a linked server in SQL Server for the folder on the web
server that actually seems to work. I also haven't found enough
documentation on what needs to be set up on both servers for this to work.
What I have done so far may be incorrect, but I have set up a linked server
like so:
sp_addlinkedserver @.server = 'FileSystem'
, @.srvproduct = 'Indexing Service'
, [ @.provider = 'MSIDXS'
, [ @.datasrc = 'FormScope'
, [ @.location = '\\devserver\wwwroot\content\production\'
, [ @.catalog = 'Web'
I have created a Full-Text catalog on the SQL Server called 'Web' and a
virtual directory on the IIS server called 'Web' that points to the devserver
folder above. When I run the search from the web site, I get this error:
An error occurred while processing your query: [OLE/DB provider returned
message: There is no catalog. ]
So I'm guessing that the catalog has not been populated with the content
from the web server, but I have no idea how to do that, or even if I'm
missing one or more steps. I'm scouring the documentation I can find but no
luck so far. Any ideas?
Karl Wiggins
This is not SQL FTS. This is using Indexing Services. You need to create a
catalog called web using the IS MMC (go to a command prompt) and type
ciadv.msc to administer it. To create the catalog in the IS MMC go to
action, new and catalog.
Then when your catalog is created right click on it and select properties
and tracking. In the WWW Server drop down box select your web server.
It also looks like you are indexing your NNTP server. Is this true?
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Karl" <kwiggins@.randallpub.com.(nospam)> wrote in message
news:BD830BC0-F393-4FBE-A1DC-EB92E2C0CE83@.microsoft.com...
> My company has a web site that we bought several years ago, and we have
had
> to replace the machines that the site runs on. I have inherited the DBA
role
> for this system recently. The site search engine has not been working for
> some time, and after digging through the asp code, I found this query:
> sSql="SELECT a.article_id,srch.size,srch.rank "&_
> "FROM OPENQUERY(FileSystem,"&_
> "'SELECT FileName, Size,rank "&_
> "FROM SCOPE('' """ & FormScope & """ '') "&_
> "WHERE CONTAINS(Contents,''" & sSearch & "'') order by rank desc,write
> desc') srch,articles a"
> if NOT isCMS Then
> sSql=sSql & ",columns c"
> End If
> sSql=sSql & " where cast(a.article_id as
varchar(15))+'.htm'=srch.filename"
> if NOT isCMS Then sSql=sSql & " AND a.status_id in (4,5) AND
> c.column_id=a.column_id
> So, after some searching, I discovered that this was using the Full-Text
> Search function in SQL Server to search through the content news articles
> under the wwwroot folder on the web server. What I'm having a hard time
> doing now is creating a linked server in SQL Server for the folder on the
web
> server that actually seems to work. I also haven't found enough
> documentation on what needs to be set up on both servers for this to work.
> What I have done so far may be incorrect, but I have set up a linked
server
> like so:
> sp_addlinkedserver @.server = 'FileSystem'
> , @.srvproduct = 'Indexing Service'
> , [ @.provider = 'MSIDXS'
> , [ @.datasrc = 'FormScope'
> , [ @.location = '\\devserver\wwwroot\content\production\'
> , [ @.catalog = 'Web'
> I have created a Full-Text catalog on the SQL Server called 'Web' and a
> virtual directory on the IIS server called 'Web' that points to the
devserver
> folder above. When I run the search from the web site, I get this error:
> An error occurred while processing your query: [OLE/DB provider returned
> message: There is no catalog. ]
> So I'm guessing that the catalog has not been populated with the content
> from the web server, but I have no idea how to do that, or even if I'm
> missing one or more steps. I'm scouring the documentation I can find but
no
> luck so far. Any ideas?
> --
> Karl Wiggins
|||Well FTS still has to be set up on the SQL Server doesn't it?
No, we aren't using NNTP, we are indexing articles in our proprietary
content-management system.
"Hilary Cotter" wrote:

> This is not SQL FTS. This is using Indexing Services. You need to create a
> catalog called web using the IS MMC (go to a command prompt) and type
> ciadv.msc to administer it. To create the catalog in the IS MMC go to
> action, new and catalog.
> Then when your catalog is created right click on it and select properties
> and tracking. In the WWW Server drop down box select your web server.
> It also looks like you are indexing your NNTP server. Is this true?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
>
> "Karl" <kwiggins@.randallpub.com.(nospam)> wrote in message
> news:BD830BC0-F393-4FBE-A1DC-EB92E2C0CE83@.microsoft.com...
> had
> role
> varchar(15))+'.htm'=srch.filename"
> web
> server
> devserver
> no
>
>
|||No you don't need SQL FTS - at least it doesn't appear you need it with the
query you have supplied.
If you don't believe me try creating a catalog called web using Ciadv.msc
and see if you still get the no catalog error.
"Karl" <kwiggins@.randallpub.com.(nospam)> wrote in message
news:F2B03DDE-C4EC-4BFF-A27C-DCC50933BA4C@.microsoft.com...[vbcol=seagreen]
> Well FTS still has to be set up on the SQL Server doesn't it?
> No, we aren't using NNTP, we are indexing articles in our proprietary
> content-management system.
> "Hilary Cotter" wrote:
|||Karl,
To clarify a couple of things... First of all, this is SQL Server T-SQL
code, just not the specific T-SQL CONTAINS implementation. The key
difference can be found in the "FROM SCOPE" spec used with OPENQUERY &
FileSystem. Normal T-SQL CONTAINS is use in a WHERE clause, such as the
below:
select * from pubs_info WHERE CONTAINS(*,'"books"')
The key error "[OLE/DB provider returned message: There is no catalog. ]"
indicates an incorrectly configured or missing Indexing Service Catalog in
the sp_addlinkedserver definition.
Regards,
John
"Karl" <kwiggins@.randallpub.com.(nospam)> wrote in message
news:F2B03DDE-C4EC-4BFF-A27C-DCC50933BA4C@.microsoft.com...[vbcol=seagreen]
> Well FTS still has to be set up on the SQL Server doesn't it?
> No, we aren't using NNTP, we are indexing articles in our proprietary
> content-management system.
> "Hilary Cotter" wrote:
a[vbcol=seagreen]
properties[vbcol=seagreen]
have[vbcol=seagreen]
DBA[vbcol=seagreen]
for[vbcol=seagreen]
Full-Text[vbcol=seagreen]
articles[vbcol=seagreen]
time[vbcol=seagreen]
the[vbcol=seagreen]
work.[vbcol=seagreen]
a[vbcol=seagreen]
error:[vbcol=seagreen]
returned[vbcol=seagreen]
content[vbcol=seagreen]
but[vbcol=seagreen]
|||Okay, I'm getting this error now:
An error occurred while processing your query: [OLE/DB provider returned
message: Multiple-step OLE DB operation generated errors. Check each OLE DB
status value, if available. No work was done.]
I set up a Indexing Services catalog called FormScope on the web server that
points to the content folder. My concern is that I don't have the linked
server on the SQL Server side set up correctly. My T-SQL code to add the
linked server looks like this:
sp_addlinkedserver @.server = 'FileSystem'
, @.srvproduct = 'Indexing Service'
, @.provider = 'MSIDXS'
, @.location = '\\DevApps03\devwwwroot\content\siteproduction\'
, @.catalog = 'FormScope'
Is this a valid location? What am I missing here?
"John Kane" wrote:

> Karl,
> To clarify a couple of things... First of all, this is SQL Server T-SQL
> code, just not the specific T-SQL CONTAINS implementation. The key
> difference can be found in the "FROM SCOPE" spec used with OPENQUERY &
> FileSystem. Normal T-SQL CONTAINS is use in a WHERE clause, such as the
> below:
> select * from pubs_info WHERE CONTAINS(*,'"books"')
> The key error "[OLE/DB provider returned message: There is no catalog. ]"
> indicates an incorrectly configured or missing Indexing Service Catalog in
> the sp_addlinkedserver definition.
> Regards,
> John
>
> "Karl" <kwiggins@.randallpub.com.(nospam)> wrote in message
> news:F2B03DDE-C4EC-4BFF-A27C-DCC50933BA4C@.microsoft.com...
> a
> properties
> have
> DBA
> for
> Full-Text
> articles
> time
> the
> work.
> a
> error:
> returned
> content
> but
>
>
|||Karl,
I think that the location spec in your sp_addlinkedserver is either
incorrect (UNC or machine_name) or not necessary when used with Indexing
Service (MSIDXS) provider. While I don't have a remote server to test this
type of configuration, I've used the following sp_addlinkedserver to define
a Linked Server to my Indexing Service Catalog on my primary server:
EXEC sp_addlinkedserver
@.server = 'lsIndexServer', -- Name
@.srvproduct = 'Index Server', -- product name of the OLE DB data source
@.provider = 'MSIDXS', -- Indexing Servics (IS) OLE DB Provider
@.datasrc = 'IS_DDrive' -- IS Catalog
go
Note, if this a Remote Indexing Service, i.e., an Indexing Service Catalog
that is not on the same server as your SQL Server, you can access it via the
following SCOPE Syntax:
Remote_Serve_rName.Remote_Server_IS_Catalogs_Name. .SCOPE(), for example:
SELECT *
FROM OPENQUERY( lsIndexServer,
'SELECT Path, Filename FROM JTKWin2003.IS_DDrive..SCOPE()
WHERE CONTAINS( ''john'' )
AND CONTAINS( ''kane'' )' ) AS jtk
Note, JTKWin2003 is my primary server name.
Thanks,
John
"Karl" <kwiggins@.randallpub.com.(nospam)> wrote in message
news:F093E09E-D972-4B4E-9503-38B0DC198EE2@.microsoft.com...
> Okay, I'm getting this error now:
> An error occurred while processing your query: [OLE/DB provider returned
> message: Multiple-step OLE DB operation generated errors. Check each OLE
DB
> status value, if available. No work was done.]
> I set up a Indexing Services catalog called FormScope on the web server
that[vbcol=seagreen]
> points to the content folder. My concern is that I don't have the linked
> server on the SQL Server side set up correctly. My T-SQL code to add the
> linked server looks like this:
> sp_addlinkedserver @.server = 'FileSystem'
> , @.srvproduct = 'Indexing Service'
> , @.provider = 'MSIDXS'
> , @.location = '\\DevApps03\devwwwroot\content\siteproduction\'
> , @.catalog = 'FormScope'
> Is this a valid location? What am I missing here?
> "John Kane" wrote:
catalog. ]"[vbcol=seagreen]
in[vbcol=seagreen]
create[vbcol=seagreen]
type[vbcol=seagreen]
to[vbcol=seagreen]
server.[vbcol=seagreen]
the[vbcol=seagreen]
working[vbcol=seagreen]
query:[vbcol=seagreen]
desc,write[vbcol=seagreen]
hard[vbcol=seagreen]
on[vbcol=seagreen]
to[vbcol=seagreen]
linked[vbcol=seagreen]
and[vbcol=seagreen]
the[vbcol=seagreen]
I'm[vbcol=seagreen]
find[vbcol=seagreen]

Full Text Setup

I'm trying to set up Full-text indexing. I installed the module, the
service shows up in control panel\services, but the option in EM is still
grayed out. Any suggestions?
FYI: SQL2000 on XP pro, rebooted machine...
thanks. -Rob T.http://www.indexserverfaq.com/tablenotenabled.htm
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rob T" <RTorcellini@.DONTwalchemSPAM.com> wrote in message
news:%23vgfkinWGHA.4960@.TK2MSFTNGP05.phx.gbl...
> I'm trying to set up Full-text indexing. I installed the module, the
> service shows up in control panel\services, but the option in EM is still
> grayed out. Any suggestions?
> FYI: SQL2000 on XP pro, rebooted machine...
> thanks. -Rob T.
>|||I've also found that if this is a remote server then the options can be
disabled, I think this is because EM can't determine if FTS is installed. I
guess its a remote permissions thing. If you log on locally you should find
it enabled
Simon Sabin
SQL Server MVP
http://sqljunkies.com/weblog/simons
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23I7E5LqWGHA.3972@.TK2MSFTNGP02.phx.gbl...
> http://www.indexserverfaq.com/tablenotenabled.htm
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rob T" <RTorcellini@.DONTwalchemSPAM.com> wrote in message
> news:%23vgfkinWGHA.4960@.TK2MSFTNGP05.phx.gbl...
>|||Not always, it seems to be a bug somewhere along the line. You can always
use the wizard from the command line to access remote SQL Servers when you
run into this problem. C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqlftwiz.exe /sRemoteServerName /n for trusted, or
/sRemoteServerName /usa /ppassword
You still need to be in the symin role on the server you are trying to
manage.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Simon Sabin" <ContactThroughMyBlog@.nospam.com> wrote in message
news:4438c2ac$1$33888$ed2619ec@.ptn-nntp-reader03.plus.net...
> I've also found that if this is a remote server then the options can be
> disabled, I think this is because EM can't determine if FTS is installed.
> I guess its a remote permissions thing. If you log on locally you should
> find it enabled
> --
> Simon Sabin
> SQL Server MVP
> http://sqljunkies.com/weblog/simons
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23I7E5LqWGHA.3972@.TK2MSFTNGP02.phx.gbl...
>|||How do I know if I am in the symin role ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OCe2ek8WGHA.3848@.TK2MSFTNGP05.phx.gbl...
> Not always, it seems to be a bug somewhere along the line. You can always
> use the wizard from the command line to access remote SQL Servers when you
> run into this problem. C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqlftwiz.exe /sRemoteServerName /n for trusted, or
> /sRemoteServerName /usa /ppassword
> You still need to be in the symin role on the server you are trying to
> manage.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Simon Sabin" <ContactThroughMyBlog@.nospam.com> wrote in message
> news:4438c2ac$1$33888$ed2619ec@.ptn-nntp-reader03.plus.net...
installed.
intelligence.
RelevantNoise's
>|||SELECT IS_SRVROLEMEMBER('symin')
*mike hodgson*
http://sqlnerd.blogspot.com
Alan wrote:

>How do I know if I am in the symin role ?
>"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
>news:OCe2ek8WGHA.3848@.TK2MSFTNGP05.phx.gbl...
>
>installed.
>
>intelligence.
>
>RelevantNoise's
>
>
>|||I tried and result is 1.|||It's documented in Books Online:
http://msdn.microsoft.com/library/e..._ia-iz_4f5e.asp
1 means the login is a member of the role.
0 means the login is not a member of the role.
*mike hodgson*
http://sqlnerd.blogspot.com
Alan wrote:

> I tried and result is 1.|||Hi Mike,
So that means my login has admin permission, right?
Do you have any idea why I cannot do a full-text search ?
"Mike Hodgson" <e1minst3r@.gmail.com> wrote in message news:OuKuWsUeGHA.1208@.
TK2MSFTNGP02.phx.gbl...
It's documented in Books Online:
http://msdn.microsoft.com/library/e..._ia-iz_4f5e.asp
1 means the login is a member of the role.
0 means the login is not a member of the role.
mike hodgson
http://sqlnerd.blogspot.com
Alan wrote:
I tried and result is 1.|||Alan wrote:

> So that means my login has admin permission, right?
Within the context of that SQL instance, yes.

> Do you have any idea why I cannot do a full-text search ?
No, sorry - I haven't been following the thread so I don't know what
problem you're experiencing exactly (I just saw your question about how
to determine if a login is a symin or not). But I'm not much of a
FTS expert anyway (I generally try to avoid FTS, initially (back in the
old days) because I found it to be a bit of a kludge, ie. being an
external service rather than core to the DB engine). Hilary & Simon
would be much better qualified to talk about FTS than I.

> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> wrote in message news:OuKuWsUeGHA.1208@.TK2MSFTNGP02.phx.gbl...
> It's documented in Books Online:
> http://msdn.microsoft.com/library/e..._ia-iz_4f5e.asp
> 1 means the login is a member of the role.
> 0 means the login is not a member of the role.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Alan wrote:
>
>
--
*mike hodgson*
http://sqlnerd.blogspot.comsql

2012年3月27日星期二

Full Text Search Setup

I am trying to setup FTS on a table in my database; the column I am
interested in FTS'ing is all image datatypes. The data in the colum is
populated via asp.net; and we store the document type as a mime type e.g.
'application/msword' as it makes it easy to get data back out from the
database.
My table has teh following columns
DocumentID UniqueIdentifier,
DocumentTypeRef int
DocumentSubject varchar(100)
DocumentValue image
DocumentDocType varchar(50)
DocumentDocType sysname -- added to use FTS would rather use vc(50) field
DocumentByteSize int
DocumentFileName varchar(100)
DocumentCreated datetime
MailMergeTemplateID uniqueidentifier
ToDoID uniqueidentifier
DocumentUploadWaiting bit
The table has 50 rows in it; in my test system. mostly word documents. I
have run teh following script to setup fts (and tried the wizard without
success)
use Activities_FTS
exec sp_fulltext_database 'enable'
exec sp_fulltext_catalog 'FTS', 'create', 'D:\\sqldata'
exec sp_fulltext_table 'tblDocuments', 'create', 'FTS', 'PK_tblDocuments'
exec sp_fulltext_column @.tabname = tblDocuments,
@.colname = DocumentValue,
@.action = 'dro',
@.Type_Colname = DocumentDocType2
exec sp_fulltext_table 'tblDocuments', 'activate'
exec sp_fulltext_table 'tblDocuments', 'start_full'
select FULLTEXTCATALOGPROPERTY('FTS', 'Populatestatus')
select * from freetexttable(tblDocuments,DocumentValue , '%%') order by
[rank] desc
This is based around the steps which worked successfully from the tutorial
on this page
http://msdn.microsoft.com/library/de...extsearch.asp.
When i run the index population check it does run for about 30 seconds; but i
cannot find out why it is not indexing the documents; or is there another
query i can use to test this. (My FTS catalog never grows above 1mb)
If you have any questions please do not hestitate to reply as i am slightly
lost now
Many thanks
Chris
Can you check what your gatherer logs report? I'm not sure if storing them
as a mime type is the best way to go.
To check your gatherer log output do this:
go to c:\program files\common files\system\mssearch\bin and copy gthrlog.vbs
to %windir% then go to your catalog location for your catalog (this should
be c:\program files\microsoft sql server\mssql\ftdata\sqlserver\gatherlogs.
Now you want to id your gatherlog for your catalog. the totally brainless
what to do this is to issue another incremental population for your catalog
and then do a dir /od. Your catalog
gather logs will then appear last in the list. The syntax is
SQLXXXXXYYYYY.?.gthr where the X is your db_id (you can determine this by
doing
this select db_id('database_name') and the YYYYYY is your catalog id, which
you can determine by doing to your database in isqlw and doing this select
id, name from syscatalogs where name ='catalog_name'.
Then with this information what you do is this (from a command prompt)
cscript gthrlog.vbs SQL0017900635.6.gthr
You will get a lot of output, but it will tell you on which row(s) the
indexer had a problem. Then what you have to do is have a look at that row
and see if you can figure out what the problem is with the data in that row
"Chris Hoare" <ChrisHoare@.discussions.microsoft.com> wrote in message
news:AB36FF24-EE13-4C7A-B8E5-E110588526CC@.microsoft.com...
>I am trying to setup FTS on a table in my database; the column I am
> interested in FTS'ing is all image datatypes. The data in the colum is
> populated via asp.net; and we store the document type as a mime type e.g.
> 'application/msword' as it makes it easy to get data back out from the
> database.
> My table has teh following columns
> DocumentID UniqueIdentifier,
> DocumentTypeRef int
> DocumentSubject varchar(100)
> DocumentValue image
> DocumentDocType varchar(50)
> DocumentDocType sysname -- added to use FTS would rather use vc(50) field
> DocumentByteSize int
> DocumentFileName varchar(100)
> DocumentCreated datetime
> MailMergeTemplateID uniqueidentifier
> ToDoID uniqueidentifier
> DocumentUploadWaiting bit
> The table has 50 rows in it; in my test system. mostly word documents. I
> have run teh following script to setup fts (and tried the wizard without
> success)
> use Activities_FTS
> exec sp_fulltext_database 'enable'
> exec sp_fulltext_catalog 'FTS', 'create', 'D:\\sqldata'
> exec sp_fulltext_table 'tblDocuments', 'create', 'FTS', 'PK_tblDocuments'
> exec sp_fulltext_column @.tabname = tblDocuments,
> @.colname = DocumentValue,
> @.action = 'dro',
> @.Type_Colname = DocumentDocType2
> exec sp_fulltext_table 'tblDocuments', 'activate'
> exec sp_fulltext_table 'tblDocuments', 'start_full'
> --
> select FULLTEXTCATALOGPROPERTY('FTS', 'Populatestatus')
> select * from freetexttable(tblDocuments,DocumentValue , '%%') order by
> [rank] desc
>
> This is based around the steps which worked successfully from the tutorial
> on this page
> http://msdn.microsoft.com/library/de...extsearch.asp.
> When i run the index population check it does run for about 30 seconds;
> but i
> cannot find out why it is not indexing the documents; or is there another
> query i can use to test this. (My FTS catalog never grows above 1mb)
> If you have any questions please do not hestitate to reply as i am
> slightly
> lost now
> Many thanks
> Chris
|||Chris,
I'm assuming that you're using SQL Server 2000 as this feature is new with
SQL Server 2000, but what OS platform is it installed on? Could you post the
full output of -- SELECT @.@.version -- as this is very helpful in
troubleshooting SQL FTS issues!
You should use the datatype of sysname (or char(3) or varchar(4)) with your
column "DocumentDocType". Could you also provide details on what values you
have populated in this column? Furthermore, how exactly did you import the
MS Word documents and what is the language of the text stored in the MS Word
documents?
Additionally, the following FREETEXTTABLE query will not return any results
as the "%" (percent) symbols are ignored by the MSSearch engine (depending
upon the OS platform):
select * from freetexttable(tblDocuments,DocumentValue , '%%') order by
[rank] desc
Instead you should use the following:
declare @.searchTerm varchar(1024)
set @.searchTerm = 'some_valid_search_word_here'
select * from freetexttable(tblDocuments, DocumentValue, @.searchTerm) order
by [rank] desc
Finally, you should review your server's Application event log for any
"Microsoft Search" or MssCi source events (warnings, informational and
errors) to determine why the initial FT Indexing is failing as this is the
only place such errors or warnings are written. Have you or anyone else
changed the SQL Server (MSSQLServer) service account &/or password via
Win2K's Component Services vs. changing this in the Enterprise Manager? If
so, then you should also review KB article 277549 (Q277549) PRB: Unable to
Build Full-Text Catalog After You Modify MSSQLServer Logon Account Through
[NT4.0) Control Panel [or Win2K Component Services] at:
http://support.microsoft.com/default...B;EN-US;277549
Regards,
John
"Chris Hoare" <ChrisHoare@.discussions.microsoft.com> wrote in message
news:AB36FF24-EE13-4C7A-B8E5-E110588526CC@.microsoft.com...
> I am trying to setup FTS on a table in my database; the column I am
> interested in FTS'ing is all image datatypes. The data in the colum is
> populated via asp.net; and we store the document type as a mime type e.g.
> 'application/msword' as it makes it easy to get data back out from the
> database.
> My table has teh following columns
> DocumentID UniqueIdentifier,
> DocumentTypeRef int
> DocumentSubject varchar(100)
> DocumentValue image
> DocumentDocType varchar(50)
> DocumentDocType sysname -- added to use FTS would rather use vc(50) field
> DocumentByteSize int
> DocumentFileName varchar(100)
> DocumentCreated datetime
> MailMergeTemplateID uniqueidentifier
> ToDoID uniqueidentifier
> DocumentUploadWaiting bit
> The table has 50 rows in it; in my test system. mostly word documents. I
> have run teh following script to setup fts (and tried the wizard without
> success)
> use Activities_FTS
> exec sp_fulltext_database 'enable'
> exec sp_fulltext_catalog 'FTS', 'create', 'D:\\sqldata'
> exec sp_fulltext_table 'tblDocuments', 'create', 'FTS', 'PK_tblDocuments'
> exec sp_fulltext_column @.tabname = tblDocuments,
> @.colname = DocumentValue,
> @.action = 'dro',
> @.Type_Colname = DocumentDocType2
> exec sp_fulltext_table 'tblDocuments', 'activate'
> exec sp_fulltext_table 'tblDocuments', 'start_full'
> --
> select FULLTEXTCATALOGPROPERTY('FTS', 'Populatestatus')
> select * from freetexttable(tblDocuments,DocumentValue , '%%') order by
> [rank] desc
>
> This is based around the steps which worked successfully from the tutorial
> on this page
>
http://msdn.microsoft.com/library/de...extsearch.asp.
> When i run the index population check it does run for about 30 seconds;
but i
> cannot find out why it is not indexing the documents; or is there another
> query i can use to test this. (My FTS catalog never grows above 1mb)
> If you have any questions please do not hestitate to reply as i am
slightly
> lost now
> Many thanks
> Chris
|||OK,
SQL Server details
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
The documents were all imported using request.file object in asp.net; and
were streamed into a stored procuedre. ASP.net can open these files again
(which is why we are storing the mime type.)
The column I referenced as DocumentDocType2 is typed as 'sysname.' this is
the column that i am referencing as Documenttype for sp_fulltext_column
I have changed the contents of the documentdoctype2 column to be both
'word' & 'msword' to be safe and run the recatalog command (Originally these
were mime types 'application/msword' or similar. In both cases this was the
result;
The application log shows the following result : Event ID 2001
"One or more documents stored in image columns with extension 'word' did not
get full-text indexed because loading the filter failed with error '0x1'.
Note: These documents will not be passed to MSSearch for indexing, and
therefore this failure will not be reflected in the end of crawl summary
statistics."
Though strangely it went on to say
"The end of crawl for project <SQLServer SQL0003400005> has been detected.
The Gatherer successfully processed 50 documents totaling 0K. It failed to
filter 0 documents. 0 URLs could not be reached or were denied access."
Finally there is an event for Master merge has completed on the index.
Thanks for your help
|||You're welcome, Chris,
Thanks for the version info as that does help, especially the fact that you
have SQL Server 2000 SP3 on Win2003! You may want to review all of the below
KB articles, and especially 326502 (Q326502) as it provides coding example
on how to use ASP.NET to load MS Word files via:
Response.AddHeader("Content-Disposition", "attachment;filename=blob.doc")
Response.ContentType = "application/msword"
The most likely cause of the Full Population failing is that only valid MS
Word (doc or .doc) files are supported when properly imported into a SQL
Server 2000 table's column defined with the IMAGE (or BLOB) datatype.
Additionally, by populating the column documentdoctype2 column with both
'word' & 'msword' will not succeed as the MSSearch service does not
recognize these as valid file extensions. See SQL Server 2000 BOL title
"Filtering Supported File Types" - specifically, "Microsoft SQL ServerT
2000 includes filters for these file extensions: .doc, .xls, .ppt, .txt, and
..htm".
I grant you that the second informational MSSearch message text was somewhat
mis-leading, but the key error "One or more documents stored in image
columns with extension 'word' did not get full-text indexed because loading
the filter failed with error '0x1'" indicates the FT Population failure
because the wrong value was placed in the documentdoctype2 column.
258038 (Q258038) HOWTO: Access and Modify SQL Server BLOB Data by Using the
ADO Stream Object
http://support.microsoft.com/?kbid=258038
309158 (Q309158) HOW TO: Read and Write BLOB Data by Using ADO.NET with C#
http://support.microsoft.com/default...b;EN-US;309158
308042 (Q308042) HOW TO: Read and Write BLOB Data by Using ADO.NET with
VB.NET
http://support.microsoft.com/default...b;EN-US;308042
326502 (Q326502) HOW TO: Read and Write BLOB Data by Using ADO.NET Through
ASP.NET
http://support.microsoft.com/?id=326502
Regards,
John
"Chris Hoare" <ChrisHoare@.discussions.microsoft.com> wrote in message
news:066C2D40-1BF5-4B26-821E-69F71F39844C@.microsoft.com...
> OK,
> SQL Server details
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> The documents were all imported using request.file object in asp.net; and
> were streamed into a stored procuedre. ASP.net can open these files again
> (which is why we are storing the mime type.)
> The column I referenced as DocumentDocType2 is typed as 'sysname.' this is
> the column that i am referencing as Documenttype for sp_fulltext_column
> I have changed the contents of the documentdoctype2 column to be both
> 'word' & 'msword' to be safe and run the recatalog command (Originally
these
> were mime types 'application/msword' or similar. In both cases this was
the
> result;
> The application log shows the following result : Event ID 2001
> "One or more documents stored in image columns with extension 'word' did
not
> get full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics."
> Though strangely it went on to say
> "The end of crawl for project <SQLServer SQL0003400005> has been detected.
> The Gatherer successfully processed 50 documents totaling 0K. It failed to
> filter 0 documents. 0 URLs could not be reached or were denied access."
> Finally there is an event for Master merge has completed on the index.
> Thanks for your help
sql

2012年3月19日星期一

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator User
Hi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator UserHi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I reposted the question in news:microsoft.public.sqlserver.programming and
received a reply from Mr. Kane who point dme to a KB that while completely
unrelated showed me where to find the Auditiong options for SQL Server which
I used to pinpoint the real problem. The problem has been resolved.
""Michael Cheng [MSFT]"" wrote:
> Hi,
> Thanks for your post.
> From your descriptions, I understood that you would like to know whether
> Full-Text Search is support in SQL Server Dev Edition and how to implement
> it. Have I understood you? Correct me if I was wrong.
> Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
> Edition on Windows XP Pro. See more deatiled descritption about this in the
> following links
> Features Supported by the Editions of SQL Server 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_ts_1cdv.asp
> For the second question, I am not sure your detailed steps on how to
> implement the Full-Text Search for the Table, would you please give me more
> detail information about doing so? Here is an sample doing this with SQL
> Server Enterprise Manager.
> 1. enable a table for full-text indexing
> - Expand Databases, expand the database in which the table belongs, and
> then click Tables.
> - In the details pane, right-click the table, click Full-Text Index Table,
> and then click Define Full-Text Indexing on a Table.
> 2. To create a full-text catalog
> - right-click the database where you want the full-text catalog.
> - Click New, and then click New Full-Text Catalog.
> - Complete the New Full-Text Catalog dialog box.
> 3. Make a Full Populating
> - expand the database that contains the full-text catalog to rebuild.
> - Click Full-Text Catalogs, and then right-click the specific catalog to
> populate.
> - Click Start Full Population
> 4. See whether the data had been updated
> - right-click the specific catalog to review.
> - Click Properties, and then click the Status, Tables, and Schedules tabs,
> as appropriate.
> See the following chapter in Books Online or MSDN Online for more detailed
> information
> Creating and Maintaining Databases -> Full-Text Indexes ->
> Administering Full-Text Features Using SQL Enterprise Manager
> Hope this helps and please feel free to let me know whether it works or you
> need furhter help. Thank you for your patience and corporation.
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi,
I have noticed that thread, it's great to hear that it was resolved and
thanks for letting me know about that:)
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Full Text Indexing on Microsoft SQL Server 2000 with Windows XP Pro

I am wondering if FUll Text Indexing is suported with MS SQL Server 2000
Developer Edition on XP Pro SP2 . I have the service installed and setup. I
have created several catalogs with data but when they are done populating
they show up with an Item Count of 0 and a Unique Index of 1 despite the
fact that there are 10+ records with extremely different data in the 3
columns that are being indexed.
I am not seeing any unusual messages in the Event Viewer also. I have
uninstalled and reinstalled already and the Server is running under an
Administrator UserHi,
Thanks for your post.
From your descriptions, I understood that you would like to know whether
Full-Text Search is support in SQL Server Dev Edition and how to implement
it. Have I understood you? Correct me if I was wrong.
Based on my scope, Full-Text Search is supported in SQL Server 2000 Dev
Edition on Windows XP Pro. See more deatiled descritption about this in the
following links
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_ts_1cdv.asp
For the second question, I am not sure your detailed steps on how to
implement the Full-Text Search for the Table, would you please give me more
detail information about doing so? Here is an sample doing this with SQL
Server Enterprise Manager.
1. enable a table for full-text indexing
- Expand Databases, expand the database in which the table belongs, and
then click Tables.
- In the details pane, right-click the table, click Full-Text Index Table,
and then click Define Full-Text Indexing on a Table.
2. To create a full-text catalog
- right-click the database where you want the full-text catalog.
- Click New, and then click New Full-Text Catalog.
- Complete the New Full-Text Catalog dialog box.
3. Make a Full Populating
- expand the database that contains the full-text catalog to rebuild.
- Click Full-Text Catalogs, and then right-click the specific catalog to
populate.
- Click Start Full Population
4. See whether the data had been updated
- right-click the specific catalog to review.
- Click Properties, and then click the Status, Tables, and Schedules tabs,
as appropriate.
See the following chapter in Books Online or MSDN Online for more detailed
information
Creating and Maintaining Databases -> Full-Text Indexes ->
Administering Full-Text Features Using SQL Enterprise Manager
Hope this helps and please feel free to let me know whether it works or you
need furhter help. Thank you for your patience and corporation.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

2012年3月9日星期五

Full text index

I am trying to setup full text search on a table.
The database has use full text indexing checked in properties.files
When I right click the table the full text selection is not there.
In other installs this table works and is setup for full text it has a key
on a single field.
What am I missing
Thank you
--
JerryHi Jerry,
I understand that you could not see the full-text index for your table when
you right clicked your table.
If I have misunderstood, please let me know.
To let me better understand your scenario, could you please let me know:
1. What is the version of your SQL Server?
2. How did you create a Full-Text index on your table?
Generally if a full-text index was correctly created,
for SQL Server 2005, you can see a table full-text index via right clicking
the table, selecting Full-Text index, and selecting Properties,
and for SQL Server 2000, you can see a table full-text index via right
clicking the table, selecting Properties, and selecting the tab "Full-Text
Searching".
You may check if you enable the table for Full-Text indexing:
How to: Enable a Table for Full-Text Indexing (SQL Server Management Studio)
http://technet.microsoft.com/en-us/library/ms142536.aspx
Full-text Querying SQL Server Data
http://msdn2.microsoft.com/en-us/library/aa172886(SQL.80).aspx
Generally to create a full-text indexing on a table, you should do the
following steps:
1. Create a full-text catalog for storing full-text indexes;
2. Define a population schedule;
3. Create a full-text index in the full-text catalog
Of course, you can use "Define Full-Text Index..." wizard (right click the
table and select Full-Text Index) in SQL 2005 Management Studio or "Define
Full-Text Indexing on a Table" wizard (right click the table and select
Full-Text Index Table) in SQL 2000 Enterprise Manager.
You may also want the following references:
Full-Text Search How-to Topics
http://technet.microsoft.com/en-us/library/ms142503.aspx
CREATE FULLTEXT INDEX (Transact-SQL)
http://technet.microsoft.com/en-us/library/ms187317.aspx
Enabling Others to Issue Full-Text Queries
http://technet.microsoft.com/en-us/library/aa214776(SQL.80).aspx
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles,
Thank you for your reply.
I am using sql server 2005.
The data base has full text enabled. Properties , Files, check full text.
and apply
The next step is to right click the table and select full text from the
menu. The full text selection is not on the menu.
Where do I go from here.
Thank you
--
Jerry
"Charles Wang[MSFT]" wrote:
> Hi Jerry,
> I understand that you could not see the full-text index for your table when
> you right clicked your table.
> If I have misunderstood, please let me know.
> To let me better understand your scenario, could you please let me know:
> 1. What is the version of your SQL Server?
> 2. How did you create a Full-Text index on your table?
> Generally if a full-text index was correctly created,
> for SQL Server 2005, you can see a table full-text index via right clicking
> the table, selecting Full-Text index, and selecting Properties,
> and for SQL Server 2000, you can see a table full-text index via right
> clicking the table, selecting Properties, and selecting the tab "Full-Text
> Searching".
> You may check if you enable the table for Full-Text indexing:
> How to: Enable a Table for Full-Text Indexing (SQL Server Management Studio)
> http://technet.microsoft.com/en-us/library/ms142536.aspx
> Full-text Querying SQL Server Data
> http://msdn2.microsoft.com/en-us/library/aa172886(SQL.80).aspx
> Generally to create a full-text indexing on a table, you should do the
> following steps:
> 1. Create a full-text catalog for storing full-text indexes;
> 2. Define a population schedule;
> 3. Create a full-text index in the full-text catalog
> Of course, you can use "Define Full-Text Index..." wizard (right click the
> table and select Full-Text Index) in SQL 2005 Management Studio or "Define
> Full-Text Indexing on a Table" wizard (right click the table and select
> Full-Text Index Table) in SQL 2000 Enterprise Manager.
> You may also want the following references:
> Full-Text Search How-to Topics
> http://technet.microsoft.com/en-us/library/ms142503.aspx
> CREATE FULLTEXT INDEX (Transact-SQL)
> http://technet.microsoft.com/en-us/library/ms187317.aspx
> Enabling Others to Issue Full-Text Queries
> http://technet.microsoft.com/en-us/library/aa214776(SQL.80).aspx
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know. Have a good day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Hi Jerry,
For further research, I would like to know:
What is the edition of your SQL Server 2005 , Express Edition or Standard
Edition or Enterprise Edition?
My test is based on SQL Server 2005 Enterprise Edition SP2.
You may first check your Services panel to ensure that SQL Server FullText
Search is there and started.
If FullText Search Services is started and this issue persists, I recommend
that you try uninstalling/reinstalling your Client Tools from Add/Remove
Programs:
Select your SQL Server 2005, click the Remove button, select the
Workstation Components and click Finish button.
After that, install the Client Tools from the Tools setup folder in your
SQL Server 2005 setup CD.
Hope this helps. If you have any questions or concerns, please feel free to
post back.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles,
Thank you for the reply.
The SQL server is the standard edition.
We uninstalled and reinstalled the workstation components and still have the
same problem.
in the step for setting up the full text:
Right click the table and select full text the full text selection in not in
the list.
The table has a single field set as a key and it is a identity column. This
works on other installs of SQL server. What could be the problem.
Thank you
Jerry
"Charles Wang[MSFT]" wrote:
> Hi Jerry,
> For further research, I would like to know:
> What is the edition of your SQL Server 2005 , Express Edition or Standard
> Edition or Enterprise Edition?
> My test is based on SQL Server 2005 Enterprise Edition SP2.
> You may first check your Services panel to ensure that SQL Server FullText
> Search is there and started.
> If FullText Search Services is started and this issue persists, I recommend
> that you try uninstalling/reinstalling your Client Tools from Add/Remove
> Programs:
> Select your SQL Server 2005, click the Remove button, select the
> Workstation Components and click Finish button.
> After that, install the Client Tools from the Tools setup folder in your
> SQL Server 2005 setup CD.
> Hope this helps. If you have any questions or concerns, please feel free to
> post back.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>|||Hi Jerry,
To let me better understand your issue, could you please mail me
(changliw_at_microsoft_dot_com) some screenshots of this issue?
If you meant that you could see "Full-Text Index" when you right clicked
the table, but that you could not define a full-text index for the table
during the "Define Full-text Index" wizard, this should be an expected
result since your table had just one column which was an identity Key
column. Only a column which type is char, nchar, varchar, nvarchar,text,
ntext, image, xml, or varbinary can be indexed for full-text search.
You may refer to:
CREATE FULLTEXT INDEX (Transact-SQL)
http://technet.microsoft.com/en-us/library/ms187317.aspx
If I have any misunderstanding, please feel free to point out. I appreciate
your mailing me the screenshots so that I can accurately understand your
issue.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles
Thank you for your reply.
I cannot see "Full-Text Index" when I right clicked the table.
There is no selection "Full-Text Index" in the popup menu when I right click
the table
Thank you
Jerry
"Charles Wang[MSFT]" wrote:
> Hi Jerry,
> To let me better understand your issue, could you please mail me
> (changliw_at_microsoft_dot_com) some screenshots of this issue?
> If you meant that you could see "Full-Text Index" when you right clicked
> the table, but that you could not define a full-text index for the table
> during the "Define Full-text Index" wizard, this should be an expected
> result since your table had just one column which was an identity Key
> column. Only a column which type is char, nchar, varchar, nvarchar,text,
> ntext, image, xml, or varbinary can be indexed for full-text search.
> You may refer to:
> CREATE FULLTEXT INDEX (Transact-SQL)
> http://technet.microsoft.com/en-us/library/ms187317.aspx
> If I have any misunderstanding, please feel free to point out. I appreciate
> your mailing me the screenshots so that I can accurately understand your
> issue.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>|||I missed beginning of this thread, so apologies of I'm off base:
Did you install full-text indexing for the instance? If not, you can add it after.
Did you create a full-text catalog for the database?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jerry C" <jerryed@.nospam.nospam> wrote in message
news:3329E859-E11A-4F39-B037-8CFCE0A03994@.microsoft.com...
> Charles
> Thank you for your reply.
> I cannot see "Full-Text Index" when I right clicked the table.
> There is no selection "Full-Text Index" in the popup menu when I right click
> the table
> Thank you
>
> --
> Jerry
>
> "Charles Wang[MSFT]" wrote:
>> Hi Jerry,
>> To let me better understand your issue, could you please mail me
>> (changliw_at_microsoft_dot_com) some screenshots of this issue?
>> If you meant that you could see "Full-Text Index" when you right clicked
>> the table, but that you could not define a full-text index for the table
>> during the "Define Full-text Index" wizard, this should be an expected
>> result since your table had just one column which was an identity Key
>> column. Only a column which type is char, nchar, varchar, nvarchar,text,
>> ntext, image, xml, or varbinary can be indexed for full-text search.
>> You may refer to:
>> CREATE FULLTEXT INDEX (Transact-SQL)
>> http://technet.microsoft.com/en-us/library/ms187317.aspx
>> If I have any misunderstanding, please feel free to point out. I appreciate
>> your mailing me the screenshots so that I can accurately understand your
>> issue.
>>
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> ======================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> ======================================================>>
>>|||Tibor,
Thank you for the reply.
I checked here for how to create a full-text catalog:
http://technet.microsoft.com/en-us/library/bb326035.aspx
in step 2:
Expand Storage, and then right-click Full Text Catalogs.
There is no Storage selection.
What could be wrong.
Thank you
--
Jerry
"Tibor Karaszi" wrote:
> I missed beginning of this thread, so apologies of I'm off base:
> Did you install full-text indexing for the instance? If not, you can add it after.
> Did you create a full-text catalog for the database?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerry C" <jerryed@.nospam.nospam> wrote in message
> news:3329E859-E11A-4F39-B037-8CFCE0A03994@.microsoft.com...
> > Charles
> >
> > Thank you for your reply.
> >
> > I cannot see "Full-Text Index" when I right clicked the table.
> >
> > There is no selection "Full-Text Index" in the popup menu when I right click
> > the table
> >
> > Thank you
> >
> >
> >
> > --
> > Jerry
> >
> >
> > "Charles Wang[MSFT]" wrote:
> >
> >> Hi Jerry,
> >> To let me better understand your issue, could you please mail me
> >> (changliw_at_microsoft_dot_com) some screenshots of this issue?
> >>
> >> If you meant that you could see "Full-Text Index" when you right clicked
> >> the table, but that you could not define a full-text index for the table
> >> during the "Define Full-text Index" wizard, this should be an expected
> >> result since your table had just one column which was an identity Key
> >> column. Only a column which type is char, nchar, varchar, nvarchar,text,
> >> ntext, image, xml, or varbinary can be indexed for full-text search.
> >> You may refer to:
> >> CREATE FULLTEXT INDEX (Transact-SQL)
> >> http://technet.microsoft.com/en-us/library/ms187317.aspx
> >>
> >> If I have any misunderstanding, please feel free to point out. I appreciate
> >> your mailing me the screenshots so that I can accurately understand your
> >> issue.
> >>
> >>
> >> Best regards,
> >> Charles Wang
> >> Microsoft Online Community Support
> >>
> >> ======================================================> >> When responding to posts, please "Reply to Group" via
> >> your newsreader so that others may learn and benefit
> >> from this issue.
> >> ======================================================> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> ======================================================> >>
> >>
> >>
> >>
> >>
>|||What version of the database engine are you using? What client tool are you using? What version of
the client tool? Are you expanding your database in Management Studio, but don't find a storage
section?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jerry C" <jerryed@.nospam.nospam> wrote in message
news:507FD33A-0F52-4255-BB97-BD0DD043C623@.microsoft.com...
> Tibor,
> Thank you for the reply.
> I checked here for how to create a full-text catalog:
> http://technet.microsoft.com/en-us/library/bb326035.aspx
> in step 2:
> Expand Storage, and then right-click Full Text Catalogs.
> There is no Storage selection.
> What could be wrong.
> Thank you
> --
> Jerry
>
> "Tibor Karaszi" wrote:
>> I missed beginning of this thread, so apologies of I'm off base:
>> Did you install full-text indexing for the instance? If not, you can add it after.
>> Did you create a full-text catalog for the database?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jerry C" <jerryed@.nospam.nospam> wrote in message
>> news:3329E859-E11A-4F39-B037-8CFCE0A03994@.microsoft.com...
>> > Charles
>> >
>> > Thank you for your reply.
>> >
>> > I cannot see "Full-Text Index" when I right clicked the table.
>> >
>> > There is no selection "Full-Text Index" in the popup menu when I right click
>> > the table
>> >
>> > Thank you
>> >
>> >
>> >
>> > --
>> > Jerry
>> >
>> >
>> > "Charles Wang[MSFT]" wrote:
>> >
>> >> Hi Jerry,
>> >> To let me better understand your issue, could you please mail me
>> >> (changliw_at_microsoft_dot_com) some screenshots of this issue?
>> >>
>> >> If you meant that you could see "Full-Text Index" when you right clicked
>> >> the table, but that you could not define a full-text index for the table
>> >> during the "Define Full-text Index" wizard, this should be an expected
>> >> result since your table had just one column which was an identity Key
>> >> column. Only a column which type is char, nchar, varchar, nvarchar,text,
>> >> ntext, image, xml, or varbinary can be indexed for full-text search.
>> >> You may refer to:
>> >> CREATE FULLTEXT INDEX (Transact-SQL)
>> >> http://technet.microsoft.com/en-us/library/ms187317.aspx
>> >>
>> >> If I have any misunderstanding, please feel free to point out. I appreciate
>> >> your mailing me the screenshots so that I can accurately understand your
>> >> issue.
>> >>
>> >>
>> >> Best regards,
>> >> Charles Wang
>> >> Microsoft Online Community Support
>> >>
>> >> ======================================================>> >> When responding to posts, please "Reply to Group" via
>> >> your newsreader so that others may learn and benefit
>> >> from this issue.
>> >> ======================================================>> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >> ======================================================>> >>
>> >>
>> >>
>> >>
>> >>|||Hi Jerry,
For further research, I would like to check with you whether you can
manually create the Full-text index on a table.
I recommend that you try the following:
1. Ensure Microsoft Full-Text Engine has been installed. You can check this
from your computer Services list. The service name is SQL Server FullText
Search (MSSQLSERVER).
2. Enable your database to using Full-text indexing via SSMS or running
sp_fulltext_database 'enable'.
3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
full-text indexes. For more information and samples, please refer to CREATE
FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
table. For more information and samples, please refer to CREATE FULLTEXT
INDEX in SQL Server 2005 Books Online.
If you can manually create the full-text index, but you still could not see
the full-text selection when you right click the table. I would like to
check with you the following information:
1. Has the latest service pack (SP2) of SQL Server 2005 been installed to
the instance of your SQL Server 2005 Standard Edition? (Run SELECT
@.@.VERSION)
If not, please try installing the SP2 to see if it helps. You can
download it from:
Microsoft SQL Server 2005 Service Pack 2
https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
-8F0C-63FA18F26D3A&displaylang=en
2. Did this issue occur on your other machine with the SQL Server 2005
Edition?
If installing SP2 could not solve the problem, please check if you can
reproduce this issue on other machine. If this issue could not be
reproduced, you may consider uninstalling/reinstalling Full-Text index
component under Database Engine to see if it helps.
From Control Panel, click Add or Remove Programs, select SQL Server
2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
Database Engine,...", click Next, select Database Engine, click Next,
follow the wizard to the Database Engine components page, select the
Full-Text index to uninstall, and click Next.
After that, reinstall the component from your SQL Server 2005 setup CD.
If this still cannot resolve the issue, I am afraid that you may consider
reinstalling your SQL Server thoroughly.
If you have any questions or concerns, please feel free to let me know.
Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles,
Thank you for the reply,
I have checked everything in the list.
Step 1 Full text is in the services list and started.
Step 2 I have run sp_fulltext_database 'enable' and it returned a success
message.
also the full text check box is checked in the database files page.
Step 3 CREATE FULLTEXT CATALOG returns a success message but I connot find a
catalog anywhere with the SQL server management studio
Step 4 CREATE FULLTEXT INDEX ran ok using this line
CREATE FULLTEXT INDEX ON Metadata KEY INDEX PK_Metadata
and it returned
A full-text index for table or indexed view 'Metadata' has already been
created.
(SP2) of SQL Server 2005 is installed the select @.@.Version
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation Express Edition with Advanced
Services on Windows NT 5.2 (Build 3790: Service Pack 2)
I will do the reinstall today and see if it helps.
Tibor, Thank you for your reply, this is the about information for this
install.
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00
(srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.2.3790
I am using sql server management studio. I expand the database and there is
no storage section.
Thank you
--
Jerry
"Charles Wang[MSFT]" wrote:
> Hi Jerry,
> For further research, I would like to check with you whether you can
> manually create the Full-text index on a table.
> I recommend that you try the following:
> 1. Ensure Microsoft Full-Text Engine has been installed. You can check this
> from your computer Services list. The service name is SQL Server FullText
> Search (MSSQLSERVER).
> 2. Enable your database to using Full-text indexing via SSMS or running
> sp_fulltext_database 'enable'.
> 3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
> full-text indexes. For more information and samples, please refer to CREATE
> FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
> 4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
> table. For more information and samples, please refer to CREATE FULLTEXT
> INDEX in SQL Server 2005 Books Online.
> If you can manually create the full-text index, but you still could not see
> the full-text selection when you right click the table. I would like to
> check with you the following information:
> 1. Has the latest service pack (SP2) of SQL Server 2005 been installed to
> the instance of your SQL Server 2005 Standard Edition? (Run SELECT
> @.@.VERSION)
> If not, please try installing the SP2 to see if it helps. You can
> download it from:
> Microsoft SQL Server 2005 Service Pack 2
> https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
> -8F0C-63FA18F26D3A&displaylang=en
> 2. Did this issue occur on your other machine with the SQL Server 2005
> Edition?
> If installing SP2 could not solve the problem, please check if you can
> reproduce this issue on other machine. If this issue could not be
> reproduced, you may consider uninstalling/reinstalling Full-Text index
> component under Database Engine to see if it helps.
> From Control Panel, click Add or Remove Programs, select SQL Server
> 2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
> Database Engine,...", click Next, select Database Engine, click Next,
> follow the wizard to the Database Engine components page, select the
> Full-Text index to uninstall, and click Next.
> After that, reinstall the component from your SQL Server 2005 setup CD.
> If this still cannot resolve the issue, I am afraid that you may consider
> reinstalling your SQL Server thoroughly.
>
> If you have any questions or concerns, please feel free to let me know.
> Have a good day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>|||Perhaps there's a bug in Management Studio, and it doesn't understand that Express with Advanced
serviced *does* include full text support. The "normal" express doesn't include full-text so perhaps
the designed of Management Studio decided to hide the FT stuff in the GUI when going against
Express...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jerry C" <jerryed@.nospam.nospam> wrote in message
news:73D51A31-83AA-4FE2-8CD9-D1E9ECDC4F43@.microsoft.com...
> Charles,
> Thank you for the reply,
> I have checked everything in the list.
> Step 1 Full text is in the services list and started.
> Step 2 I have run sp_fulltext_database 'enable' and it returned a success
> message.
> also the full text check box is checked in the database files page.
> Step 3 CREATE FULLTEXT CATALOG returns a success message but I connot find a
> catalog anywhere with the SQL server management studio
> Step 4 CREATE FULLTEXT INDEX ran ok using this line
> CREATE FULLTEXT INDEX ON Metadata KEY INDEX PK_Metadata
> and it returned
> A full-text index for table or indexed view 'Metadata' has already been
> created.
> (SP2) of SQL Server 2005 is installed the select @.@.Version
> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07
> Copyright (c) 1988-2005 Microsoft Corporation Express Edition with Advanced
> Services on Windows NT 5.2 (Build 3790: Service Pack 2)
> I will do the reinstall today and see if it helps.
> Tibor, Thank you for your reply, this is the about information for this
> install.
> Microsoft SQL Server Management Studio 9.00.3042.00
> Microsoft Analysis Services Client Tools 2005.090.3042.00
> Microsoft Data Access Components (MDAC) 2000.086.3959.00
> (srv03_sp2_rtm.070216-1710)
> Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
> Microsoft Internet Explorer 7.0.5730.11
> Microsoft .NET Framework 2.0.50727.832
> Operating System 5.2.3790
>
> I am using sql server management studio. I expand the database and there is
> no storage section.
> Thank you
> --
> Jerry
>
> "Charles Wang[MSFT]" wrote:
>> Hi Jerry,
>> For further research, I would like to check with you whether you can
>> manually create the Full-text index on a table.
>> I recommend that you try the following:
>> 1. Ensure Microsoft Full-Text Engine has been installed. You can check this
>> from your computer Services list. The service name is SQL Server FullText
>> Search (MSSQLSERVER).
>> 2. Enable your database to using Full-text indexing via SSMS or running
>> sp_fulltext_database 'enable'.
>> 3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
>> full-text indexes. For more information and samples, please refer to CREATE
>> FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
>> 4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
>> table. For more information and samples, please refer to CREATE FULLTEXT
>> INDEX in SQL Server 2005 Books Online.
>> If you can manually create the full-text index, but you still could not see
>> the full-text selection when you right click the table. I would like to
>> check with you the following information:
>> 1. Has the latest service pack (SP2) of SQL Server 2005 been installed to
>> the instance of your SQL Server 2005 Standard Edition? (Run SELECT
>> @.@.VERSION)
>> If not, please try installing the SP2 to see if it helps. You can
>> download it from:
>> Microsoft SQL Server 2005 Service Pack 2
>> https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
>> -8F0C-63FA18F26D3A&displaylang=en
>> 2. Did this issue occur on your other machine with the SQL Server 2005
>> Edition?
>> If installing SP2 could not solve the problem, please check if you can
>> reproduce this issue on other machine. If this issue could not be
>> reproduced, you may consider uninstalling/reinstalling Full-Text index
>> component under Database Engine to see if it helps.
>> From Control Panel, click Add or Remove Programs, select SQL Server
>> 2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
>> Database Engine,...", click Next, select Database Engine, click Next,
>> follow the wizard to the Database Engine components page, select the
>> Full-Text index to uninstall, and click Next.
>> After that, reinstall the component from your SQL Server 2005 setup CD.
>> If this still cannot resolve the issue, I am afraid that you may consider
>> reinstalling your SQL Server thoroughly.
>>
>> If you have any questions or concerns, please feel free to let me know.
>> Have a good day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> ======================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> ======================================================>>
>>
>>|||FWIW, the SQL Server Management Studio Express does not have GUI support
for FT stuff either. The online tutorial at Microsoft walks you through the
commands. See video 13 at:
http://msdn2.microsoft.com/en-us/express/aa718391.aspx
RLF
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:C0FB3D8E-9BB7-451C-B8F9-8DA7569C93A0@.microsoft.com...
> Perhaps there's a bug in Management Studio, and it doesn't understand that
> Express with Advanced serviced *does* include full text support. The
> "normal" express doesn't include full-text so perhaps the designed of
> Management Studio decided to hide the FT stuff in the GUI when going
> against Express...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerry C" <jerryed@.nospam.nospam> wrote in message
> news:73D51A31-83AA-4FE2-8CD9-D1E9ECDC4F43@.microsoft.com...
>> Charles,
>> Thank you for the reply,
>> I have checked everything in the list.
>> Step 1 Full text is in the services list and started.
>> Step 2 I have run sp_fulltext_database 'enable' and it returned a success
>> message.
>> also the full text check box is checked in the database files page.
>> Step 3 CREATE FULLTEXT CATALOG returns a success message but I connot
>> find a
>> catalog anywhere with the SQL server management studio
>> Step 4 CREATE FULLTEXT INDEX ran ok using this line
>> CREATE FULLTEXT INDEX ON Metadata KEY INDEX PK_Metadata
>> and it returned
>> A full-text index for table or indexed view 'Metadata' has already been
>> created.
>> (SP2) of SQL Server 2005 is installed the select @.@.Version
>> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007
>> 22:47:07
>> Copyright (c) 1988-2005 Microsoft Corporation Express Edition with
>> Advanced
>> Services on Windows NT 5.2 (Build 3790: Service Pack 2)
>> I will do the reinstall today and see if it helps.
>> Tibor, Thank you for your reply, this is the about information for this
>> install.
>> Microsoft SQL Server Management Studio 9.00.3042.00
>> Microsoft Analysis Services Client Tools 2005.090.3042.00
>> Microsoft Data Access Components (MDAC) 2000.086.3959.00
>> (srv03_sp2_rtm.070216-1710)
>> Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
>> Microsoft Internet Explorer 7.0.5730.11
>> Microsoft .NET Framework 2.0.50727.832
>> Operating System 5.2.3790
>>
>> I am using sql server management studio. I expand the database and there
>> is
>> no storage section.
>> Thank you
>> --
>> Jerry
>>
>> "Charles Wang[MSFT]" wrote:
>> Hi Jerry,
>> For further research, I would like to check with you whether you can
>> manually create the Full-text index on a table.
>> I recommend that you try the following:
>> 1. Ensure Microsoft Full-Text Engine has been installed. You can check
>> this
>> from your computer Services list. The service name is SQL Server
>> FullText
>> Search (MSSQLSERVER).
>> 2. Enable your database to using Full-text indexing via SSMS or running
>> sp_fulltext_database 'enable'.
>> 3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
>> full-text indexes. For more information and samples, please refer to
>> CREATE
>> FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
>> 4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
>> table. For more information and samples, please refer to CREATE FULLTEXT
>> INDEX in SQL Server 2005 Books Online.
>> If you can manually create the full-text index, but you still could not
>> see
>> the full-text selection when you right click the table. I would like to
>> check with you the following information:
>> 1. Has the latest service pack (SP2) of SQL Server 2005 been installed
>> to
>> the instance of your SQL Server 2005 Standard Edition? (Run SELECT
>> @.@.VERSION)
>> If not, please try installing the SP2 to see if it helps. You can
>> download it from:
>> Microsoft SQL Server 2005 Service Pack 2
>> https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
>> -8F0C-63FA18F26D3A&displaylang=en
>> 2. Did this issue occur on your other machine with the SQL Server 2005
>> Edition?
>> If installing SP2 could not solve the problem, please check if you
>> can
>> reproduce this issue on other machine. If this issue could not be
>> reproduced, you may consider uninstalling/reinstalling Full-Text index
>> component under Database Engine to see if it helps.
>> From Control Panel, click Add or Remove Programs, select SQL Server
>> 2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
>> Database Engine,...", click Next, select Database Engine, click Next,
>> follow the wizard to the Database Engine components page, select the
>> Full-Text index to uninstall, and click Next.
>> After that, reinstall the component from your SQL Server 2005 setup
>> CD.
>> If this still cannot resolve the issue, I am afraid that you may
>> consider
>> reinstalling your SQL Server thoroughly.
>>
>> If you have any questions or concerns, please feel free to let me know.
>> Have a good day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> ======================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> ======================================================>>
>>
>>
>|||Charles and Tibor,
I have another machine without this problem the versions of management
studio are below.
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Thank you
Jerry
"Charles Wang[MSFT]" wrote:
> Hi Jerry,
> For further research, I would like to check with you whether you can
> manually create the Full-text index on a table.
> I recommend that you try the following:
> 1. Ensure Microsoft Full-Text Engine has been installed. You can check this
> from your computer Services list. The service name is SQL Server FullText
> Search (MSSQLSERVER).
> 2. Enable your database to using Full-text indexing via SSMS or running
> sp_fulltext_database 'enable'.
> 3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
> full-text indexes. For more information and samples, please refer to CREATE
> FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
> 4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
> table. For more information and samples, please refer to CREATE FULLTEXT
> INDEX in SQL Server 2005 Books Online.
> If you can manually create the full-text index, but you still could not see
> the full-text selection when you right click the table. I would like to
> check with you the following information:
> 1. Has the latest service pack (SP2) of SQL Server 2005 been installed to
> the instance of your SQL Server 2005 Standard Edition? (Run SELECT
> @.@.VERSION)
> If not, please try installing the SP2 to see if it helps. You can
> download it from:
> Microsoft SQL Server 2005 Service Pack 2
> https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
> -8F0C-63FA18F26D3A&displaylang=en
> 2. Did this issue occur on your other machine with the SQL Server 2005
> Edition?
> If installing SP2 could not solve the problem, please check if you can
> reproduce this issue on other machine. If this issue could not be
> reproduced, you may consider uninstalling/reinstalling Full-Text index
> component under Database Engine to see if it helps.
> From Control Panel, click Add or Remove Programs, select SQL Server
> 2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
> Database Engine,...", click Next, select Database Engine, click Next,
> follow the wizard to the Database Engine components page, select the
> Full-Text index to uninstall, and click Next.
> After that, reinstall the component from your SQL Server 2005 setup CD.
> If this still cannot resolve the issue, I am afraid that you may consider
> reinstalling your SQL Server thoroughly.
>
> If you have any questions or concerns, please feel free to let me know.
> Have a good day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>|||Perhaps SSMS originally showed FT stuff against the regular Express (which doesn't have FT), and
that was considered a but. Then this was fixed in a later build of SSMS so it doesn't show FT stuff
against express. That would be a good thing when going against the regular express, but would have
been a bad thing when going against express with advanced services. Just speculation, I should
add...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jerry C" <jerryed@.nospam.nospam> wrote in message
news:CF15E37B-ED04-4FA2-91B3-57C3A91833A3@.microsoft.com...
> Charles and Tibor,
> I have another machine without this problem the versions of management
> studio are below.
> Microsoft SQL Server Management Studio 9.00.1399.00
> Microsoft Analysis Services Client Tools 2005.090.1399.00
> Thank you
>
>
> --
> Jerry
>
> "Charles Wang[MSFT]" wrote:
>> Hi Jerry,
>> For further research, I would like to check with you whether you can
>> manually create the Full-text index on a table.
>> I recommend that you try the following:
>> 1. Ensure Microsoft Full-Text Engine has been installed. You can check this
>> from your computer Services list. The service name is SQL Server FullText
>> Search (MSSQLSERVER).
>> 2. Enable your database to using Full-text indexing via SSMS or running
>> sp_fulltext_database 'enable'.
>> 3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
>> full-text indexes. For more information and samples, please refer to CREATE
>> FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
>> 4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
>> table. For more information and samples, please refer to CREATE FULLTEXT
>> INDEX in SQL Server 2005 Books Online.
>> If you can manually create the full-text index, but you still could not see
>> the full-text selection when you right click the table. I would like to
>> check with you the following information:
>> 1. Has the latest service pack (SP2) of SQL Server 2005 been installed to
>> the instance of your SQL Server 2005 Standard Edition? (Run SELECT
>> @.@.VERSION)
>> If not, please try installing the SP2 to see if it helps. You can
>> download it from:
>> Microsoft SQL Server 2005 Service Pack 2
>> https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
>> -8F0C-63FA18F26D3A&displaylang=en
>> 2. Did this issue occur on your other machine with the SQL Server 2005
>> Edition?
>> If installing SP2 could not solve the problem, please check if you can
>> reproduce this issue on other machine. If this issue could not be
>> reproduced, you may consider uninstalling/reinstalling Full-Text index
>> component under Database Engine to see if it helps.
>> From Control Panel, click Add or Remove Programs, select SQL Server
>> 2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
>> Database Engine,...", click Next, select Database Engine, click Next,
>> follow the wizard to the Database Engine components page, select the
>> Full-Text index to uninstall, and click Next.
>> After that, reinstall the component from your SQL Server 2005 setup CD.
>> If this still cannot resolve the issue, I am afraid that you may consider
>> reinstalling your SQL Server thoroughly.
>>
>> If you have any questions or concerns, please feel free to let me know.
>> Have a good day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> ======================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> ======================================================>>
>>
>>|||Hi Jerry,
Thanks for your feedback.
I think that we got the point here. I noticed that you said that your SQL
Server 2005 was standard edition before, however from your last response it
was SQL Server 2005 Express Edition with Advanced Services. So I guess that
your current SSMS is SSMSE (SQL Server Management Studio Express) which
does not include UI features for supporting Full-text indexing. Originally
SQL Server 2005 Express did not support Full-text indexing until SQL Server
2005 Express with Advanced Services was released.
Currently in SSMSE you must manually create Full-text indexing by hand. If
you want to use the UI features, you need to install SSMS from your SQL
Server 2005 STD/ENT/DEV Edition setup CD. I think that the SSMS worked on
your other machine was not a Express edition. You can run SELECT @.@.VERSION
to check this.
There is a video regarding Full-text indexing in SQL Server 2005 Express
with Advanced Services in Microsoft site. You may refer to:
http://download.microsoft.com/download/b/3/8/b3847275-2bea-440a-8e2e-305b009
bb261/sql_13.wmv
Hope this helps. If you have any other questions or concerns, please feel
free to let us know. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Tibor, Charles,
That must be the problem. When I checked the properties of the data base
there is a line that identifies the server as a express version. Sorry I did
not notice this long ago.
I unstalled that server and am working on installing a Standard Edition of
the server.
The problem I ran into now is the Standard Edition will not install on this
machine. The error is Unknown error.
I think I will rebuild this machine.
Thank you
--
Jerry
"Tibor Karaszi" wrote:
> Perhaps SSMS originally showed FT stuff against the regular Express (which doesn't have FT), and
> that was considered a but. Then this was fixed in a later build of SSMS so it doesn't show FT stuff
> against express. That would be a good thing when going against the regular express, but would have
> been a bad thing when going against express with advanced services. Just speculation, I should
> add...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerry C" <jerryed@.nospam.nospam> wrote in message
> news:CF15E37B-ED04-4FA2-91B3-57C3A91833A3@.microsoft.com...
> > Charles and Tibor,
> >
> > I have another machine without this problem the versions of management
> > studio are below.
> >
> > Microsoft SQL Server Management Studio 9.00.1399.00
> > Microsoft Analysis Services Client Tools 2005.090.1399.00
> > Thank you
> >
> >
> >
> >
> > --
> > Jerry
> >
> >
> > "Charles Wang[MSFT]" wrote:
> >
> >> Hi Jerry,
> >> For further research, I would like to check with you whether you can
> >> manually create the Full-text index on a table.
> >> I recommend that you try the following:
> >> 1. Ensure Microsoft Full-Text Engine has been installed. You can check this
> >> from your computer Services list. The service name is SQL Server FullText
> >> Search (MSSQLSERVER).
> >> 2. Enable your database to using Full-text indexing via SSMS or running
> >> sp_fulltext_database 'enable'.
> >> 3. Manually run CREATE FULLTEXT CATALOG to create a catalog for storing
> >> full-text indexes. For more information and samples, please refer to CREATE
> >> FULLTEXT CATALOG (Transact-SQL) in SQL Server 2005 Books Online.
> >> 4. Manually run CREATE FULLTEXT INDEX to create a full-text index on a
> >> table. For more information and samples, please refer to CREATE FULLTEXT
> >> INDEX in SQL Server 2005 Books Online.
> >>
> >> If you can manually create the full-text index, but you still could not see
> >> the full-text selection when you right click the table. I would like to
> >> check with you the following information:
> >> 1. Has the latest service pack (SP2) of SQL Server 2005 been installed to
> >> the instance of your SQL Server 2005 Standard Edition? (Run SELECT
> >> @.@.VERSION)
> >> If not, please try installing the SP2 to see if it helps. You can
> >> download it from:
> >> Microsoft SQL Server 2005 Service Pack 2
> >>
> >> https://www.microsoft.com/downloads/details.aspx?familyid=D07219B2-1E23-49C8
> >> -8F0C-63FA18F26D3A&displaylang=en
> >>
> >> 2. Did this issue occur on your other machine with the SQL Server 2005
> >> Edition?
> >> If installing SP2 could not solve the problem, please check if you can
> >> reproduce this issue on other machine. If this issue could not be
> >> reproduced, you may consider uninstalling/reinstalling Full-Text index
> >> component under Database Engine to see if it helps.
> >> From Control Panel, click Add or Remove Programs, select SQL Server
> >> 2005, click Change, select SQL Server 2005 Instances-> "MSSQLSERVER:
> >> Database Engine,...", click Next, select Database Engine, click Next,
> >> follow the wizard to the Database Engine components page, select the
> >> Full-Text index to uninstall, and click Next.
> >> After that, reinstall the component from your SQL Server 2005 setup CD.
> >> If this still cannot resolve the issue, I am afraid that you may consider
> >> reinstalling your SQL Server thoroughly.
> >>
> >>
> >> If you have any questions or concerns, please feel free to let me know.
> >> Have a good day!
> >>
> >> Best regards,
> >> Charles Wang
> >> Microsoft Online Community Support
> >>
> >> ======================================================> >> When responding to posts, please "Reply to Group" via
> >> your newsreader so that others may learn and benefit
> >> from this issue.
> >> ======================================================> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> ======================================================> >>
> >>
> >>
> >>
> >>
> >>
>|||Hi Jerry,
You may try uninstalling all the SQL Server 2005 components from Add or
Remove Programs and then delete the existing legacy folders, restart your
computer and install your SQL Server 2005 STD edition.
Please note that backup your databases before you perform the above action.
If you have any other questions or concerns, please feel free to let us
know. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================