Hi,
I'm putting together a system and one of the requirements is to have a
searchable CV function.
I've got all the code to load the files on to the image fields, I've indexed
and got it mostly working.
Before I go to far down the road what is your opinion on having txt files
instead of doc files to search? The SQL seems to be more flexible on
searches rather than on the binary files and the index files themselves are
smaller.
My main concern is I'd have to do the text conversion automatically, any
pointers on this?
Does anyone have any views on the best way to go about this
Many thanks for any help you can give
Jim FlorenceHave you tried asking this in the sqlserver.fulltext news group?
As long as all expected binary types are supported by appropriate IFilters
on your server, using binary data will be just fine - AFAIK.
ML
http://milambda.blogspot.com/|||Thanks for the pointer, embarrassingly I didn't see it existed :0/
I just noticed on trying one query with "select like" it would only work on
varchar fields and failed on the blob, could well be mistaken though.
Thanks again
Jim
"ML" <ML@.discussions.microsoft.com> wrote in message
news:45DBD971-2EE7-42C5-AD3A-C3F542B4F8DA@.microsoft.com...
> Have you tried asking this in the sqlserver.fulltext news group?
> As long as all expected binary types are supported by appropriate IFilters
> on your server, using binary data will be just fine - AFAIK.
>
> ML
> --
> http://milambda.blogspot.com/|||The LIKE operatoron binary values works if the searched string is cast to
binary or varbinary, but only if the binary column contains a true
representation of the text, which is not how Word documents are represented.
What exactly did you try?
BTW: with FTI you really shouldn't use the LIKE operator - FTS functions are
more efficient in this case.
ML
http://milambda.blogspot.com/|||Thaks for thatr I knew I'd have missed something obvious.
I'm not entierly sure what the difference is between FTI and FTS, I thought
they were one and the same
Jim
"ML" <ML@.discussions.microsoft.com> wrote in message
news:29D91E26-BE4C-4832-B888-8FA47423C793@.microsoft.com...
> The LIKE operatoron binary values works if the searched string is cast to
> binary or varbinary, but only if the binary column contains a true
> representation of the text, which is not how Word documents are
> represented.
> What exactly did you try?
> BTW: with FTI you really shouldn't use the LIKE operator - FTS functions
> are
> more efficient in this case.
>
> ML
> --
> http://milambda.blogspot.com/|||Jim,
I am trying to do something similar. I have a list of .doc files that I am
trying to do i full text search on. I would really appreciate some help on
how to do this. Some sql code would be great. Thanks
qtrsteve@.yahoo.com|||Sorry for a late reply.
FTS = full-text search
FTI = full-text index
FTS uses FTI.
I was referring to FTS functions: contains, containstable, frettext,
freetexttable. FTS functions are far more efficient than the LIKE operator,
or at least the processing overhead of FTS is pretty constant compared to th
e
overhead when using the LIKE operator.
ML
http://milambda.blogspot.com/sql
2012年3月27日星期二
2012年3月26日星期一
full text search on doc files
I have a list of word files (.doc) I am trying to us the full text
search in sql server to find key words in these word documents. I have
a Windows XP and sql server installed on my machine. ( no network
server). I cant seem to get the code to work to do a search on these
files. I would really appreciate if someone can send me some code from
start to finsh so I can create the sql tables and then catolog to
search for keywords in the word files.What version of SQL Server are you using? Word documents must be stored in
columns of data type image, and another column must be present to store the
type suffix (".doc" for MS Word files).
When full-text indexing is activated for an image column the name of the
column where the suffix is stored must also be set. How this is actually don
e
depends on the SQL Server version.
SQL 2000:
sp_fulltext_column
@.tabname = '<qualified_table_name>'
,@.colname = '<column_name>'
,@.action = 'add'
,@.type_colname = '<type_column_name>'
SQL 2005:
create fulltext index on <table_name>
(<column_name> TYPE COLUMN <type_column_name>
key index <index_name>
If the index has been created appropriately, then you might also check the
SQL Error Log:
http://milambda.blogspot.com/2005/1...n-or-bybug.html
ML
http://milambda.blogspot.com/|||ML,
How do i create the table first and get the files indexed? How do I
get the files catologued? i am using sql2000 . Do i run the sql you
wrote above after the files have been imported?|||Setting up full-text indexing in SQL 2000 is very well documented in Books
Online:
http://msdn.microsoft.com/library/d... />
d_6g1f.asp
After you've created the table and enabled the database for full-text
search, you need to enable the table, then the column for full-text indexing
.
It really doesn't matter whether you set up FTI before inserting data in the
tables, or after, as long as you propagate change to the catalogue before yo
u
try to use full-text search (new rows will not be found by the engine until
the contents have been indexed).
There are several methods of propagating change to the full-text catalogue:
full propagation, incremental propagation and background propagation (with
change tracking). With background propagation new rows are indexed after
they've been inserted and changed rows are indexed after they've been
updated, but there's a performance impact and writetext/updatetext operation
s
are not detected.
To avoid the downside you could use incremental propagation by creating a
SQL Agent Job that starts incremental propagation as frequently as you need.
Are you having any specific problems? You could also ask these questions in
the dedicated newsgorup: "microsoft.public.sqlserver.fulltext".
ML
http://milambda.blogspot.com/|||ML,
I have looked through the link, still not getting it to work. I guess
i need some code, from start to finish, loading the file from the
c:\... and then running the sql. Anything you may have would be
extremely helpful..thanks|||The link I sent you will help you set up full-text indexing, but the actual
method of inserting MS Word documents into the table depends on your client
application.
If you need to insert blobs through T-SQL, you could use BULK INSERT:
http://msdn.microsoft.com/library/d...br />
4fec.asp
Also make sure you create the format file in accordance to this KB article:
http://support.microsoft.com/defaul...kb;en-us;271344
Information on using format files:
http://msdn.microsoft.com/library/d...>
bcp_9yat.asp
ML
http://milambda.blogspot.com/
search in sql server to find key words in these word documents. I have
a Windows XP and sql server installed on my machine. ( no network
server). I cant seem to get the code to work to do a search on these
files. I would really appreciate if someone can send me some code from
start to finsh so I can create the sql tables and then catolog to
search for keywords in the word files.What version of SQL Server are you using? Word documents must be stored in
columns of data type image, and another column must be present to store the
type suffix (".doc" for MS Word files).
When full-text indexing is activated for an image column the name of the
column where the suffix is stored must also be set. How this is actually don
e
depends on the SQL Server version.
SQL 2000:
sp_fulltext_column
@.tabname = '<qualified_table_name>'
,@.colname = '<column_name>'
,@.action = 'add'
,@.type_colname = '<type_column_name>'
SQL 2005:
create fulltext index on <table_name>
(<column_name> TYPE COLUMN <type_column_name>
key index <index_name>
If the index has been created appropriately, then you might also check the
SQL Error Log:
http://milambda.blogspot.com/2005/1...n-or-bybug.html
ML
http://milambda.blogspot.com/|||ML,
How do i create the table first and get the files indexed? How do I
get the files catologued? i am using sql2000 . Do i run the sql you
wrote above after the files have been imported?|||Setting up full-text indexing in SQL 2000 is very well documented in Books
Online:
http://msdn.microsoft.com/library/d... />
d_6g1f.asp
After you've created the table and enabled the database for full-text
search, you need to enable the table, then the column for full-text indexing
.
It really doesn't matter whether you set up FTI before inserting data in the
tables, or after, as long as you propagate change to the catalogue before yo
u
try to use full-text search (new rows will not be found by the engine until
the contents have been indexed).
There are several methods of propagating change to the full-text catalogue:
full propagation, incremental propagation and background propagation (with
change tracking). With background propagation new rows are indexed after
they've been inserted and changed rows are indexed after they've been
updated, but there's a performance impact and writetext/updatetext operation
s
are not detected.
To avoid the downside you could use incremental propagation by creating a
SQL Agent Job that starts incremental propagation as frequently as you need.
Are you having any specific problems? You could also ask these questions in
the dedicated newsgorup: "microsoft.public.sqlserver.fulltext".
ML
http://milambda.blogspot.com/|||ML,
I have looked through the link, still not getting it to work. I guess
i need some code, from start to finish, loading the file from the
c:\... and then running the sql. Anything you may have would be
extremely helpful..thanks|||The link I sent you will help you set up full-text indexing, but the actual
method of inserting MS Word documents into the table depends on your client
application.
If you need to insert blobs through T-SQL, you could use BULK INSERT:
http://msdn.microsoft.com/library/d...br />
4fec.asp
Also make sure you create the format file in accordance to this KB article:
http://support.microsoft.com/defaul...kb;en-us;271344
Information on using format files:
http://msdn.microsoft.com/library/d...>
bcp_9yat.asp
ML
http://milambda.blogspot.com/
2012年3月21日星期三
Full Text Search - Thesaurus
Dear All,
I am not able to activate thesaurus in SQL Server 2005. With some help I was able to use noise files but thesaurus is uphill. The following is my tsENU.xml file:
<XML ID="Microsoft Search Thesaurus">
<thesaurus xmlns="x-schema:tsSchema.xml">
<diacritics_sensitive>0</diacritics_sensitive>
<expansion>
<sub>ANTHONY</sub>
<sub>TONY</sub>
</expansion>
</thesaurus>
</XML>
All I want is, ANTHONY and TONY to be treated as synonymous.
The following is my query:
SELECT CONTACTID, FULLNAME
FROM CONTACT
WHERE CONTAINS (FULLNAME, ' FORMSOF (THESAURUS, TONY) ')
and
SELECT CONTACTID, FULLNAME
FROM CONTACT
WHERE FREETEXT (FULLNAME, 'TONY')
To no awail. Am I missing some thing here? Kindly help me to go thru this.
I even restarted the sqlftservice and recreated the index but to no use.
thanks and regards
SQLDBA123
Here is an example thesaurus file:
<XML ID="Microsoft Search Thesaurus">
<thesaurus xmlns="x-schema:tsSchema.xml">
<diacritics = false/>
<replacement>
<pat>W2K</pat>
<sub>Windows 2000</sub>
<sub>NT</sub>
</replacement>
<replacement>
<pat>Internet Explorer</pat>
<sub>IE</sub>
<sub>IE 5</sub>
</replacement>
<replacement>
<pat>Internet</pat>
<sub>intranet</sub>
</replacement>
<expansion>
<sub>run</sub>
<sub>jog</sub>
</expansion>
<replacement>
<pat>seek</pat>
<sub>went</sub>
</replacement>
</thesaurus>
</XML>
Please replace the corresponding thesaurus with this example and restart msftesql service. Now thesaurus should work. The problem is that the example in the thesaurus file is wrong on diacritics setting property.
thanks,
Jingwei
Full Text Search - Thesaurus
Dear All,
I am not able to activate thesaurus in SQL Server 2005. With some help I was able to use noise files but thesaurus is uphill. The following is my tsENU.xml file:
<XML ID="Microsoft Search Thesaurus">
<thesaurus xmlns="x-schema:tsSchema.xml">
<diacritics_sensitive>0</diacritics_sensitive>
<expansion>
<sub>ANTHONY</sub>
<sub>TONY</sub>
</expansion>
</thesaurus>
</XML>
All I want is, ANTHONY and TONY to be treated as synonymous.
The following is my query:
SELECT CONTACTID, FULLNAME
FROM CONTACT
WHERE CONTAINS (FULLNAME, ' FORMSOF (THESAURUS, TONY) ')
and
SELECT CONTACTID, FULLNAME
FROM CONTACT
WHERE FREETEXT (FULLNAME, 'TONY')
To no awail. Am I missing some thing here? Kindly help me to go thru this.
I even restarted the sqlftservice and recreated the index but to no use.
thanks and regards
SQLDBA123
Here is an example thesaurus file:
<XML ID="Microsoft Search Thesaurus">
<thesaurus xmlns="x-schema:tsSchema.xml">
<diacritics = false/>
<replacement>
<pat>W2K</pat>
<sub>Windows 2000</sub>
<sub>NT</sub>
</replacement>
<replacement>
<pat>Internet Explorer</pat>
<sub>IE</sub>
<sub>IE 5</sub>
</replacement>
<replacement>
<pat>Internet</pat>
<sub>intranet</sub>
</replacement>
<expansion>
<sub>run</sub>
<sub>jog</sub>
</expansion>
<replacement>
<pat>seek</pat>
<sub>went</sub>
</replacement>
</thesaurus>
</XML>
Please replace the corresponding thesaurus with this example and restart msftesql service. Now thesaurus should work. The problem is that the example in the thesaurus file is wrong on diacritics setting property.
thanks,
Jingwei
2012年3月11日星期日
Full Text Indexing Error
I see a lot of these in my Event log on the SQL Server for my Windows
Sharepoint Services site.
It would be nice to know what files are not being indexed and why.
Posting in the WSS group got me advice to update to SQL Server SP3 (done at
install) and/or post here.
Event Log Messages:
One or more documents stored in image columns with extension 'xls' 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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
One or more documents stored in image columns with extension '' 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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This normally means your iFilter or related components has/have crashed. Try
to bounce MSSearch to solve this problem.You may need to reboot your server.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||OK
A little more information...
The server is rebooted weekly
These errors have been cropping up for a while - So far i have had no
reports from users of any problems, but they are not using Sharepoint's
search very extensivly yet.
I hope to change that, but want to have some confidence in the results.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OnhOjEkAFHA.4028@.TK2MSFTNGP15.phx.gbl...
> This normally means your iFilter or related components has/have crashed.
Try
> to bounce MSSearch to solve this problem.You may need to reboot your
server.[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>
|||David,
The first event log error indicates that an Excel (*.xls) file did not get
FT Indexed and the 2nd event log error indicates that a file extension of
'' (or NULL) did not get FT Indexed. The former, may occur because of a bad
file, but the latter should not occur, unless you are storing un-known
extensions. You should examine the gather log files (*.gthr) under
\FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
information and post the output of the gthrlog.vbs utility.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||John,
Thanks for the quick reply.
I had to switch to my network, security and training hats respectivly but am
now under the Sharepoint hat and have the following result:
1/31/2005 12:55:34 AM Add The gatherer has started
1/31/2005 12:55:36 AM Add The initialization has completed
1/31/2005 8:57:26 AM
MSSQL75://SQLServer/1de57479/CB325AA2334BED409E0F527D35A87A67 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 10:20:06 AM
MSSQL75://SQLServer/1de57479/EBB20D5D67E2EC4F820041532CB288BC Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/76cba758/A86817082BA3E0469D8D07C2D70A8905 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/1de57479/C774194838E91540868BDAF8027CCEC8 Add Error
fetching URL, (80041201 - The object was not found. )
Clear enough, some reference is either expired or corrupt.
In your experience, is this something to be concerned about?
Searches have become much slower than the last time I tried anything, but we
also have 4 or 5 gb more data.
Bt slow, I mean durations of minutes while the SQL Server (dual pentium 4
2.something with 4gb ram) shows 80-95% processor consumed by MSSEARCH.
My users are not making much use of Search in Sharepoint, and at this point
I am holding off on encouraging them
David
btw - Nice pic on your blog - I really need to get out skiing again one of
these years...
"John Kane" <jt-kane@.comcast.net> wrote in message
news:uTVnh0pAFHA.1404@.TK2MSFTNGP11.phx.gbl...
> David,
> The first event log error indicates that an Excel (*.xls) file did not get
> FT Indexed and the 2nd event log error indicates that a file extension of
> '' (or NULL) did not get FT Indexed. The former, may occur because of a
bad[vbcol=seagreen]
> file, but the latter should not occur, unless you are storing un-known
> extensions. You should examine the gather log files (*.gthr) under
> \FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
> information and post the output of the gthrlog.vbs utility.
> Thanks,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>
Sharepoint Services site.
It would be nice to know what files are not being indexed and why.
Posting in the WSS group got me advice to update to SQL Server SP3 (done at
install) and/or post here.
Event Log Messages:
One or more documents stored in image columns with extension 'xls' 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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
One or more documents stored in image columns with extension '' 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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This normally means your iFilter or related components has/have crashed. Try
to bounce MSSearch to solve this problem.You may need to reboot your server.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||OK
A little more information...
The server is rebooted weekly
These errors have been cropping up for a while - So far i have had no
reports from users of any problems, but they are not using Sharepoint's
search very extensivly yet.
I hope to change that, but want to have some confidence in the results.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OnhOjEkAFHA.4028@.TK2MSFTNGP15.phx.gbl...
> This normally means your iFilter or related components has/have crashed.
Try
> to bounce MSSearch to solve this problem.You may need to reboot your
server.[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>
|||David,
The first event log error indicates that an Excel (*.xls) file did not get
FT Indexed and the 2nd event log error indicates that a file extension of
'' (or NULL) did not get FT Indexed. The former, may occur because of a bad
file, but the latter should not occur, unless you are storing un-known
extensions. You should examine the gather log files (*.gthr) under
\FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
information and post the output of the gthrlog.vbs utility.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' 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.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||John,
Thanks for the quick reply.
I had to switch to my network, security and training hats respectivly but am
now under the Sharepoint hat and have the following result:
1/31/2005 12:55:34 AM Add The gatherer has started
1/31/2005 12:55:36 AM Add The initialization has completed
1/31/2005 8:57:26 AM
MSSQL75://SQLServer/1de57479/CB325AA2334BED409E0F527D35A87A67 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 10:20:06 AM
MSSQL75://SQLServer/1de57479/EBB20D5D67E2EC4F820041532CB288BC Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/76cba758/A86817082BA3E0469D8D07C2D70A8905 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/1de57479/C774194838E91540868BDAF8027CCEC8 Add Error
fetching URL, (80041201 - The object was not found. )
Clear enough, some reference is either expired or corrupt.
In your experience, is this something to be concerned about?
Searches have become much slower than the last time I tried anything, but we
also have 4 or 5 gb more data.
Bt slow, I mean durations of minutes while the SQL Server (dual pentium 4
2.something with 4gb ram) shows 80-95% processor consumed by MSSEARCH.
My users are not making much use of Search in Sharepoint, and at this point
I am holding off on encouraging them
David
btw - Nice pic on your blog - I really need to get out skiing again one of
these years...
"John Kane" <jt-kane@.comcast.net> wrote in message
news:uTVnh0pAFHA.1404@.TK2MSFTNGP11.phx.gbl...
> David,
> The first event log error indicates that an Excel (*.xls) file did not get
> FT Indexed and the 2nd event log error indicates that a file extension of
> '' (or NULL) did not get FT Indexed. The former, may occur because of a
bad[vbcol=seagreen]
> file, but the latter should not occur, unless you are storing un-known
> extensions. You should examine the gather log files (*.gthr) under
> \FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
> information and post the output of the gthrlog.vbs utility.
> Thanks,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>
Full text indexes files missing?
I have a full text index...in the properties of the index the path
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.
They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
Hilary Cotter
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
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegro ups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.
They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
Hilary Cotter
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
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegro ups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>
Full text indexes files missing?
I have a full text index...in the properties of the index the path
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
--
Hilary Cotter
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
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegroups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
--
Hilary Cotter
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
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegroups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>
Full text indexes files missing?
I have a full text index...in the properties of the index the path
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
Hilary Cotter
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
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegroups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>
shows...
C:\Program Files\Microsoft SQL Server\MSSQL\FTData
But if I look in the directory...I see nothing.
Yet...the system still lets me repopulate the index.
Is this normal? Should the index files be in this directory?
I searched the system for the .gthr files...and It shows them on the
D:\MSSQL\FTDATA directory.
This seems odd to me.They don't have to be in this directory, issue the following stored
procedure to find out where your files are
sp_help_fulltext_catalogs
Note the path column.
Hilary Cotter
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
<mchi55@.hotmail.com> wrote in message
news:1168226858.291120.304230@.11g2000cwr.googlegroups.com...
>I have a full text index...in the properties of the index the path
> shows...
> C:\Program Files\Microsoft SQL Server\MSSQL\FTData
>
> But if I look in the directory...I see nothing.
> Yet...the system still lets me repopulate the index.
> Is this normal? Should the index files be in this directory?
> I searched the system for the .gthr files...and It shows them on the
> D:\MSSQL\FTDATA directory.
> This seems odd to me.
>
Full text index removal
RESTORE FILELISTONLY
FROM DISK = 'C:\Full0100.BAK'
Here is the result
database d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\database
..mdf
database _Log d:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\database _log.ldf
sysft_PhraseologyIndex d:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\FTData\PhraseologyIndex
I would like to remove the sysft_PhraseologyIndex. The database server does
not have full-text component installed (this particular database was created
with sql server 2000 that supported the full-text indexing and upgraded to
sql server 2005 that does not support full-text index)
Thanks
You need to disable full-text indexing and then remove the
sysft_phraseologyindex file.
"iiman" <nospam@.nospam.com> wrote in message
news:evP$tdahHHA.1220@.TK2MSFTNGP03.phx.gbl...
> RESTORE FILELISTONLY
> FROM DISK = 'C:\Full0100.BAK'
> Here is the result
> database d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\database
> .mdf
> database _Log d:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\database _log.ldf
> sysft_PhraseologyIndex d:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\FTData\PhraseologyIndex
> I would like to remove the sysft_PhraseologyIndex. The database server
> does
> not have full-text component installed (this particular database was
> created
> with sql server 2000 that supported the full-text indexing and upgraded to
> sql server 2005 that does not support full-text index)
> Thanks
>
>
|||I tried,
ALTER DATABASE scope
REMOVE FILE sysft_PhraseologyIndex
I get
Msg 5020, Level 16, State 1, Line 1
The primary data or log file cannot be removed from a database.
How do I remove the file?
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e$8GzmhhHHA.4596@.TK2MSFTNGP05.phx.gbl...
> You need to disable full-text indexing and then remove the
> sysft_phraseologyindex file.
> "iiman" <nospam@.nospam.com> wrote in message
> news:evP$tdahHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
FROM DISK = 'C:\Full0100.BAK'
Here is the result
database d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\database
..mdf
database _Log d:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\database _log.ldf
sysft_PhraseologyIndex d:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\FTData\PhraseologyIndex
I would like to remove the sysft_PhraseologyIndex. The database server does
not have full-text component installed (this particular database was created
with sql server 2000 that supported the full-text indexing and upgraded to
sql server 2005 that does not support full-text index)
Thanks
You need to disable full-text indexing and then remove the
sysft_phraseologyindex file.
"iiman" <nospam@.nospam.com> wrote in message
news:evP$tdahHHA.1220@.TK2MSFTNGP03.phx.gbl...
> RESTORE FILELISTONLY
> FROM DISK = 'C:\Full0100.BAK'
> Here is the result
> database d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\database
> .mdf
> database _Log d:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\database _log.ldf
> sysft_PhraseologyIndex d:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\FTData\PhraseologyIndex
> I would like to remove the sysft_PhraseologyIndex. The database server
> does
> not have full-text component installed (this particular database was
> created
> with sql server 2000 that supported the full-text indexing and upgraded to
> sql server 2005 that does not support full-text index)
> Thanks
>
>
|||I tried,
ALTER DATABASE scope
REMOVE FILE sysft_PhraseologyIndex
I get
Msg 5020, Level 16, State 1, Line 1
The primary data or log file cannot be removed from a database.
How do I remove the file?
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e$8GzmhhHHA.4596@.TK2MSFTNGP05.phx.gbl...
> You need to disable full-text indexing and then remove the
> sysft_phraseologyindex file.
> "iiman" <nospam@.nospam.com> wrote in message
> news:evP$tdahHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
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.
======================================================
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.
======================================================
Full Text Filter (pdf)
After searching the internet for a way to add an IFilter for pdf files, I
found instructions to do this. I downloaded the Adobe filter (version 6), and
ran the installation.
Then, as per the instructions, ran sp_fulltext_service 'load_os_resources',1
and
sp_fulltext_service 'verify_signature', 0.
I see the pdf filter in sys.fulltext_document_types, however when I try to
search in a pdf doc in the database, I don't get any results. I have
re-imported the pdf file into the database, but this made no difference.
I also made sure the pdf document was not a scanned image, but is actual
text (I did some editing to make sure).
Any ideas what I'm missing here?
Thanks for any help,
Tomt
Hi Tomt,
I understand that although you installed Adobe filter you still could not
perform full-text index query on your document column which stored your pdf
document.
If I have misunderstood, please let me know.
I performed a test at my side and everything worked fine. I recommend that
you check if your steps were same as follows:
1. Store your pdf file in a varbinary column and meanwhile specify an
extension column.
For example:
CREATE TABLE [dbo].[Dictionary](
[ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
[Doc] [varbinary](max) NULL,
[FileExtension] [nchar](10) NULL,
)
2. Download and install the PDF Filter
(http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
3. Execute the following to enable:
exec sp_fulltext_service 'load_os_resources',1
exec sp_fulltext_service 'verify_signature', 0
4. Create and populate your full-text index. For example:
ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
=1024KB )
TO FILEGROUP [FullText]
Go
CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
'F:\TempData' AS DEFAULT;
Go
CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
Go
After above steps, you may need to wait a while for SQL Server finishing
full population.
One thing you need pay attention to is that you shoud specify a file
extention column for specifying the document extention name "pdf".
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
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 Charles, thanks for your response.
I had already gone thru all the steps (and had things working for Word docs,
for example). I added the pdf filter after everything else was set up, then
imported a pdf document with the pdf extension in a column FileExtension, and
the actual file in a column Document.
The table works fine for Word docs, but not for the pdf. Should I just start
all over again? Would it matter that the Adobe filter was added after the
table was created and the catalog set up?
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> I understand that although you installed Adobe filter you still could not
> perform full-text index query on your document column which stored your pdf
> document.
> If I have misunderstood, please let me know.
> I performed a test at my side and everything worked fine. I recommend that
> you check if your steps were same as follows:
> 1. Store your pdf file in a varbinary column and meanwhile specify an
> extension column.
> For example:
> CREATE TABLE [dbo].[Dictionary](
> [ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
> [Doc] [varbinary](max) NULL,
> [FileExtension] [nchar](10) NULL,
> )
> 2. Download and install the PDF Filter
> (http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
> 3. Execute the following to enable:
> exec sp_fulltext_service 'load_os_resources',1
> exec sp_fulltext_service 'verify_signature', 0
> 4. Create and populate your full-text index. For example:
> ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
> FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
> =1024KB )
> TO FILEGROUP [FullText]
> Go
> CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
> 'F:\TempData' AS DEFAULT;
> Go
> CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
> INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
> Go
> After above steps, you may need to wait a while for SQL Server finishing
> full population.
> One thing you need pay attention to is that you shoud specify a file
> extention column for specifying the document extention name "pdf".
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> 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 Tomt,
There are something differences between storing a PDF and a Word document.
SQL Server 2005 has built-in support for Full-text index on Word document.
You can even directly store a .doc document into a nvarchar(max) field and
no need to specify a file extension for it.
You may consider performing a SQL Server restart to see if it helps. If
not, drop the existing Full-text index and catalog and then perform a fresh
re-creation of them.
If this issue persists, could you please let me know the version of your
SQL Server 2005 and how you imported your .pdf file into the database
table? My test was on SQL Server 2005 SP2 (9.0.3054).
Look forward to your response and 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.
================================================== ====
|||Charles, I removed the index and catalog and re-created them, and re-started
the services and all seems to be working properly now: I can search in pdf's.
Thanks very much for your assistance with this...
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> There are something differences between storing a PDF and a Word document.
> SQL Server 2005 has built-in support for Full-text index on Word document.
> You can even directly store a .doc document into a nvarchar(max) field and
> no need to specify a file extension for it.
> You may consider performing a SQL Server restart to see if it helps. If
> not, drop the existing Full-text index and catalog and then perform a fresh
> re-creation of them.
> If this issue persists, could you please let me know the version of your
> SQL Server 2005 and how you imported your .pdf file into the database
> table? My test was on SQL Server 2005 SP2 (9.0.3054).
> Look forward to your response and 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.
> ================================================== ====
>
>
>
>
>
>
found instructions to do this. I downloaded the Adobe filter (version 6), and
ran the installation.
Then, as per the instructions, ran sp_fulltext_service 'load_os_resources',1
and
sp_fulltext_service 'verify_signature', 0.
I see the pdf filter in sys.fulltext_document_types, however when I try to
search in a pdf doc in the database, I don't get any results. I have
re-imported the pdf file into the database, but this made no difference.
I also made sure the pdf document was not a scanned image, but is actual
text (I did some editing to make sure).
Any ideas what I'm missing here?
Thanks for any help,
Tomt
Hi Tomt,
I understand that although you installed Adobe filter you still could not
perform full-text index query on your document column which stored your pdf
document.
If I have misunderstood, please let me know.
I performed a test at my side and everything worked fine. I recommend that
you check if your steps were same as follows:
1. Store your pdf file in a varbinary column and meanwhile specify an
extension column.
For example:
CREATE TABLE [dbo].[Dictionary](
[ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
[Doc] [varbinary](max) NULL,
[FileExtension] [nchar](10) NULL,
)
2. Download and install the PDF Filter
(http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
3. Execute the following to enable:
exec sp_fulltext_service 'load_os_resources',1
exec sp_fulltext_service 'verify_signature', 0
4. Create and populate your full-text index. For example:
ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
=1024KB )
TO FILEGROUP [FullText]
Go
CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
'F:\TempData' AS DEFAULT;
Go
CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
Go
After above steps, you may need to wait a while for SQL Server finishing
full population.
One thing you need pay attention to is that you shoud specify a file
extention column for specifying the document extention name "pdf".
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
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 Charles, thanks for your response.
I had already gone thru all the steps (and had things working for Word docs,
for example). I added the pdf filter after everything else was set up, then
imported a pdf document with the pdf extension in a column FileExtension, and
the actual file in a column Document.
The table works fine for Word docs, but not for the pdf. Should I just start
all over again? Would it matter that the Adobe filter was added after the
table was created and the catalog set up?
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> I understand that although you installed Adobe filter you still could not
> perform full-text index query on your document column which stored your pdf
> document.
> If I have misunderstood, please let me know.
> I performed a test at my side and everything worked fine. I recommend that
> you check if your steps were same as follows:
> 1. Store your pdf file in a varbinary column and meanwhile specify an
> extension column.
> For example:
> CREATE TABLE [dbo].[Dictionary](
> [ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
> [Doc] [varbinary](max) NULL,
> [FileExtension] [nchar](10) NULL,
> )
> 2. Download and install the PDF Filter
> (http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
> 3. Execute the following to enable:
> exec sp_fulltext_service 'load_os_resources',1
> exec sp_fulltext_service 'verify_signature', 0
> 4. Create and populate your full-text index. For example:
> ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
> FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
> =1024KB )
> TO FILEGROUP [FullText]
> Go
> CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
> 'F:\TempData' AS DEFAULT;
> Go
> CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
> INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
> Go
> After above steps, you may need to wait a while for SQL Server finishing
> full population.
> One thing you need pay attention to is that you shoud specify a file
> extention column for specifying the document extention name "pdf".
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> 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 Tomt,
There are something differences between storing a PDF and a Word document.
SQL Server 2005 has built-in support for Full-text index on Word document.
You can even directly store a .doc document into a nvarchar(max) field and
no need to specify a file extension for it.
You may consider performing a SQL Server restart to see if it helps. If
not, drop the existing Full-text index and catalog and then perform a fresh
re-creation of them.
If this issue persists, could you please let me know the version of your
SQL Server 2005 and how you imported your .pdf file into the database
table? My test was on SQL Server 2005 SP2 (9.0.3054).
Look forward to your response and 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.
================================================== ====
|||Charles, I removed the index and catalog and re-created them, and re-started
the services and all seems to be working properly now: I can search in pdf's.
Thanks very much for your assistance with this...
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> There are something differences between storing a PDF and a Word document.
> SQL Server 2005 has built-in support for Full-text index on Word document.
> You can even directly store a .doc document into a nvarchar(max) field and
> no need to specify a file extension for it.
> You may consider performing a SQL Server restart to see if it helps. If
> not, drop the existing Full-text index and catalog and then perform a fresh
> re-creation of them.
> If this issue persists, could you please let me know the version of your
> SQL Server 2005 and how you imported your .pdf file into the database
> table? My test was on SQL Server 2005 SP2 (9.0.3054).
> Look forward to your response and 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.
> ================================================== ====
>
>
>
>
>
>
Full Text Filter (pdf)
After searching the internet for a way to add an IFilter for pdf files, I
found instructions to do this. I downloaded the Adobe filter (version 6), and
ran the installation.
Then, as per the instructions, ran sp_fulltext_service 'load_os_resources',1
and
sp_fulltext_service 'verify_signature', 0.
I see the pdf filter in sys.fulltext_document_types, however when I try to
search in a pdf doc in the database, I don't get any results. I have
re-imported the pdf file into the database, but this made no difference.
I also made sure the pdf document was not a scanned image, but is actual
text (I did some editing to make sure).
Any ideas what I'm missing here?
Thanks for any help,
TomtHi Tomt,
I understand that although you installed Adobe filter you still could not
perform full-text index query on your document column which stored your pdf
document.
If I have misunderstood, please let me know.
I performed a test at my side and everything worked fine. I recommend that
you check if your steps were same as follows:
1. Store your pdf file in a varbinary column and meanwhile specify an
extension column.
For example:
CREATE TABLE [dbo].[Dictionary](
[ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
[Doc] [varbinary](max) NULL,
[FileExtension] [nchar](10) NULL,
)
2. Download and install the PDF Filter
(http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
3. Execute the following to enable:
exec sp_fulltext_service 'load_os_resources',1
exec sp_fulltext_service 'verify_signature', 0
4. Create and populate your full-text index. For example:
ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
=1024KB )
TO FILEGROUP [FullText]
Go
CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
'F:\TempData' AS DEFAULT;
Go
CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
Go
After above steps, you may need to wait a while for SQL Server finishing
full population.
One thing you need pay attention to is that you shoud specify a file
extention column for specifying the document extention name "pdf".
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
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 Charles, thanks for your response.
I had already gone thru all the steps (and had things working for Word docs,
for example). I added the pdf filter after everything else was set up, then
imported a pdf document with the pdf extension in a column FileExtension, and
the actual file in a column Document.
The table works fine for Word docs, but not for the pdf. Should I just start
all over again? Would it matter that the Adobe filter was added after the
table was created and the catalog set up?
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> I understand that although you installed Adobe filter you still could not
> perform full-text index query on your document column which stored your pdf
> document.
> If I have misunderstood, please let me know.
> I performed a test at my side and everything worked fine. I recommend that
> you check if your steps were same as follows:
> 1. Store your pdf file in a varbinary column and meanwhile specify an
> extension column.
> For example:
> CREATE TABLE [dbo].[Dictionary](
> [ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
> [Doc] [varbinary](max) NULL,
> [FileExtension] [nchar](10) NULL,
> )
> 2. Download and install the PDF Filter
> (http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
> 3. Execute the following to enable:
> exec sp_fulltext_service 'load_os_resources',1
> exec sp_fulltext_service 'verify_signature', 0
> 4. Create and populate your full-text index. For example:
> ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
> FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
> =1024KB )
> TO FILEGROUP [FullText]
> Go
> CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
> 'F:\TempData' AS DEFAULT;
> Go
> CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
> INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
> Go
> After above steps, you may need to wait a while for SQL Server finishing
> full population.
> One thing you need pay attention to is that you shoud specify a file
> extention column for specifying the document extention name "pdf".
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> 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 Tomt,
There are something differences between storing a PDF and a Word document.
SQL Server 2005 has built-in support for Full-text index on Word document.
You can even directly store a .doc document into a nvarchar(max) field and
no need to specify a file extension for it.
You may consider performing a SQL Server restart to see if it helps. If
not, drop the existing Full-text index and catalog and then perform a fresh
re-creation of them.
If this issue persists, could you please let me know the version of your
SQL Server 2005 and how you imported your .pdf file into the database
table? My test was on SQL Server 2005 SP2 (9.0.3054).
Look forward to your response and 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.
======================================================|||Charles, I removed the index and catalog and re-created them, and re-started
the services and all seems to be working properly now: I can search in pdf's.
Thanks very much for your assistance with this...
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> There are something differences between storing a PDF and a Word document.
> SQL Server 2005 has built-in support for Full-text index on Word document.
> You can even directly store a .doc document into a nvarchar(max) field and
> no need to specify a file extension for it.
> You may consider performing a SQL Server restart to see if it helps. If
> not, drop the existing Full-text index and catalog and then perform a fresh
> re-creation of them.
> If this issue persists, could you please let me know the version of your
> SQL Server 2005 and how you imported your .pdf file into the database
> table? My test was on SQL Server 2005 SP2 (9.0.3054).
> Look forward to your response and 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.
> ======================================================>
>
>
>
>
>
found instructions to do this. I downloaded the Adobe filter (version 6), and
ran the installation.
Then, as per the instructions, ran sp_fulltext_service 'load_os_resources',1
and
sp_fulltext_service 'verify_signature', 0.
I see the pdf filter in sys.fulltext_document_types, however when I try to
search in a pdf doc in the database, I don't get any results. I have
re-imported the pdf file into the database, but this made no difference.
I also made sure the pdf document was not a scanned image, but is actual
text (I did some editing to make sure).
Any ideas what I'm missing here?
Thanks for any help,
TomtHi Tomt,
I understand that although you installed Adobe filter you still could not
perform full-text index query on your document column which stored your pdf
document.
If I have misunderstood, please let me know.
I performed a test at my side and everything worked fine. I recommend that
you check if your steps were same as follows:
1. Store your pdf file in a varbinary column and meanwhile specify an
extension column.
For example:
CREATE TABLE [dbo].[Dictionary](
[ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
[Doc] [varbinary](max) NULL,
[FileExtension] [nchar](10) NULL,
)
2. Download and install the PDF Filter
(http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
3. Execute the following to enable:
exec sp_fulltext_service 'load_os_resources',1
exec sp_fulltext_service 'verify_signature', 0
4. Create and populate your full-text index. For example:
ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
=1024KB )
TO FILEGROUP [FullText]
Go
CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
'F:\TempData' AS DEFAULT;
Go
CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
Go
After above steps, you may need to wait a while for SQL Server finishing
full population.
One thing you need pay attention to is that you shoud specify a file
extention column for specifying the document extention name "pdf".
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
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 Charles, thanks for your response.
I had already gone thru all the steps (and had things working for Word docs,
for example). I added the pdf filter after everything else was set up, then
imported a pdf document with the pdf extension in a column FileExtension, and
the actual file in a column Document.
The table works fine for Word docs, but not for the pdf. Should I just start
all over again? Would it matter that the Adobe filter was added after the
table was created and the catalog set up?
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> I understand that although you installed Adobe filter you still could not
> perform full-text index query on your document column which stored your pdf
> document.
> If I have misunderstood, please let me know.
> I performed a test at my side and everything worked fine. I recommend that
> you check if your steps were same as follows:
> 1. Store your pdf file in a varbinary column and meanwhile specify an
> extension column.
> For example:
> CREATE TABLE [dbo].[Dictionary](
> [ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
> [Doc] [varbinary](max) NULL,
> [FileExtension] [nchar](10) NULL,
> )
> 2. Download and install the PDF Filter
> (http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
> 3. Execute the following to enable:
> exec sp_fulltext_service 'load_os_resources',1
> exec sp_fulltext_service 'verify_signature', 0
> 4. Create and populate your full-text index. For example:
> ALTER DATABASE TestDB ADD FILE ( NAME = N'TestDBFT_data',
> FILENAME = N'F:\TempData\TestDBFT_data.ndf' , SIZE = 2048KB , FILEGROWTH
> =1024KB )
> TO FILEGROUP [FullText]
> Go
> CREATE FULLTEXT CATALOG TestDBCatalog ON FILEGROUP FullText IN PATH
> 'F:\TempData' AS DEFAULT;
> Go
> CREATE FULLTEXT INDEX ON Dictionary ([Doc] TYPE COLUMN FileExtension) KEY
> INDEX PK_Dictionary ON TestDBCatalog WITH CHANGE_TRACKING AUTO;
> Go
> After above steps, you may need to wait a while for SQL Server finishing
> full population.
> One thing you need pay attention to is that you shoud specify a file
> extention column for specifying the document extention name "pdf".
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> 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 Tomt,
There are something differences between storing a PDF and a Word document.
SQL Server 2005 has built-in support for Full-text index on Word document.
You can even directly store a .doc document into a nvarchar(max) field and
no need to specify a file extension for it.
You may consider performing a SQL Server restart to see if it helps. If
not, drop the existing Full-text index and catalog and then perform a fresh
re-creation of them.
If this issue persists, could you please let me know the version of your
SQL Server 2005 and how you imported your .pdf file into the database
table? My test was on SQL Server 2005 SP2 (9.0.3054).
Look forward to your response and 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.
======================================================|||Charles, I removed the index and catalog and re-created them, and re-started
the services and all seems to be working properly now: I can search in pdf's.
Thanks very much for your assistance with this...
"Charles Wang[MSFT]" wrote:
> Hi Tomt,
> There are something differences between storing a PDF and a Word document.
> SQL Server 2005 has built-in support for Full-text index on Word document.
> You can even directly store a .doc document into a nvarchar(max) field and
> no need to specify a file extension for it.
> You may consider performing a SQL Server restart to see if it helps. If
> not, drop the existing Full-text index and catalog and then perform a fresh
> re-creation of them.
> If this issue persists, could you please let me know the version of your
> SQL Server 2005 and how you imported your .pdf file into the database
> table? My test was on SQL Server 2005 SP2 (9.0.3054).
> Look forward to your response and 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.
> ======================================================>
>
>
>
>
>
订阅：
博文 (Atom)