Fulltext Thesaurus

My understanding of the fulltext search using the thesaurus function is that
it will not work until the TSxxx.XML file is populated (in my case the
tsENU.xml file.)
Is this true?
We rae migrating from SQL 2000 and I could have sworn this was working there
.
Maybe I am mistaken.
I do see where the MS Office products use the MSTH3AM.LEX & MSTH3BR.LEX
dictionary files to support the thesaurus lookup there. Can these files
somehow be migrated over to SQL Server 2005 for use there or somehow be read
and converted to an XML thesaurus?
Thomas MannHere's a thought......I believe MS Word was installed on the machine that
had SQL 2000 on it.
I know that when I set up a new desktop, spellcheck & thesaurus are not
available to other applications (i.e. Outlook Express) until after MS Word i
s
installed.
Could this be the reason the Thesaurus funtion worked on the previous
machine and not the machine running SQL 2005?
--
Thomas Mann|||I have opened a trouble ticket on this issue and will continue to post
updates as this progresses (so you don't have to.)
What I have found thus far is that the standard advice of removing the
commented xml code in the tsENU.xml file does not cut it. Once you do this,
the xml tries to reference the schema (tsSchema.xml) which is missing from
the SQL Server 2005 install. I located a copy of the file from an earlier
version (SQL 2000 SP3) and that solved my missing schema problem but still
the Thesaurus function would not work (even after adding the substituion
params in tsENU.xml.)
I burned one of my support incidents from my MSDN subscription and contacted
the support center. They checked several of the machines there and could not
find the missing schema file amoungst the installed files either.
Bottom line, it sounds like this might be an install problem (or an
undocumented feature.)
I will post the fix here when I find out more.
--
Thomas Mann

fulltext statistics

Hi all,
Is it possible to get statistics of any sort from the full text engine?
My understanding is SQL Server treats the the fulltext engine as a remote
server and performs distributed queries against it via oledb. AFAIK, oledb
has optional interfaces to obtain stats (cardinality, distribution) which the
fulltext engine presumably supports since it comes up with reasonable
estimates in estimated query plans involving containstable.
So using an estimated plan is one way to get cardinality estimates for a
particular query, but I'm wondering if there's a more direct approach -- e.g.
I'd really like to be able to just get a histogram of terms. Perhaps it's
possible to connect directly to the full text engine via oledb? If so, what
would the connection string look like? or...?
Thanks for any ideas.
-Geoff
This is supposed to ship in SQL 2008.
http://www.zetainteractive.com - Shift Happens!
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
"Geoff Chappell" <GeoffChappell@.discussions.microsoft.com> wrote in message
news:95516FF5-7316-437D-9278-0463823A028B@.microsoft.com...
> Hi all,
> Is it possible to get statistics of any sort from the full text engine?
> My understanding is SQL Server treats the the fulltext engine as a remote
> server and performs distributed queries against it via oledb. AFAIK, oledb
> has optional interfaces to obtain stats (cardinality, distribution) which
> the
> fulltext engine presumably supports since it comes up with reasonable
> estimates in estimated query plans involving containstable.
> So using an estimated plan is one way to get cardinality estimates for a
> particular query, but I'm wondering if there's a more direct approach --
> e.g.
> I'd really like to be able to just get a histogram of terms. Perhaps it's
> possible to connect directly to the full text engine via oledb? If so,
> what
> would the connection string look like? or...?
> Thanks for any ideas.
> -Geoff
>
>
>

Full-Text search and database view

My understanding from full-text search (with SQL 2000) is that you can only
search a table and not a view; i.e. you cannot create a full-text index for
a view.
1) Is there a way to full-text search a view?
2) If not, what could I be using the search data in the database using a
view which is better (faster) than a "LIKE "?
Thanks...
Denis.
In SQL 2005 you can full text index and search views.
Currently in SQL 2000 you can't full text index views, so you will have to
materialize the view as a table, i.e. create a table which has the same
columns as a view and use replication or triggers to keep this table in sync
with the base table. Then FTI this table.
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
"Denis Blondeau" <denisblondeau@.hotmail.com> wrote in message
news:uaa144dGFHA.400@.TK2MSFTNGP14.phx.gbl...
> My understanding from full-text search (with SQL 2000) is that you can
only
> search a table and not a view; i.e. you cannot create a full-text index
for
> a view.
> 1) Is there a way to full-text search a view?
> 2) If not, what could I be using the search data in the database using a
> view which is better (faster) than a "LIKE "?
> Thanks...
> Denis.
>
|||Denis,
Yes, your understanding is correct for SQL Server 2000.
1) Is there a way to full-text search a view?
A. You cannot FT Index the "contents" of a view, however, you can include
SQL FTS statements such as CONTAINS or FREETEXT in a view.
2) If not, what could I be using the search data in the database using a
view which is better (faster) than a "LIKE "?
A. Depending upon your requirements (and more info on this would be
helpful), and assuming that you want to use FTS to search either multiple
columns or multiple tables & column in one SQL FTS statement, you may want
to checkout "SQL Server FTS across multiple tables or columns" at
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!316.entry
If you have further questions on how to enhance SQL FTS, feel free to leave
a comment!
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Denis Blondeau" <denisblondeau@.hotmail.com> wrote in message
news:uaa144dGFHA.400@.TK2MSFTNGP14.phx.gbl...
> My understanding from full-text search (with SQL 2000) is that you can
only
> search a table and not a view; i.e. you cannot create a full-text index
for
> a view.
> 1) Is there a way to full-text search a view?
> 2) If not, what could I be using the search data in the database using a
> view which is better (faster) than a "LIKE "?
> Thanks...
> Denis.
>
|||Thanks for your help, John (and Hilary)!
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OttF9zhGFHA.2524@.TK2MSFTNGP15.phx.gbl...
> Denis,
> Yes, your understanding is correct for SQL Server 2000.
> 1) Is there a way to full-text search a view?
> A. You cannot FT Index the "contents" of a view, however, you can include
> SQL FTS statements such as CONTAINS or FREETEXT in a view.
> 2) If not, what could I be using the search data in the database using a
> view which is better (faster) than a "LIKE "?
> A. Depending upon your requirements (and more info on this would be
> helpful), and assuming that you want to use FTS to search either multiple
> columns or multiple tables & column in one SQL FTS statement, you may want
> to checkout "SQL Server FTS across multiple tables or columns" at
>
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!316.entry
> If you have further questions on how to enhance SQL FTS, feel free to
leave
> a comment!
> Thanks,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Denis Blondeau" <denisblondeau@.hotmail.com> wrote in message
> news:uaa144dGFHA.400@.TK2MSFTNGP14.phx.gbl...
> only
> for
>