This sounds great. Being able to see the indexed words and the docids they
belong to will help alot with the text mining we are hoping to do. The search
performance gains will be very welcome as well.
I have a few questions:
When you mention that the filestream function means that the blob no longer
needs to be stored in the database, does this also mean that the text output
from the IFilters or stellant can also be stored in the filestream and not in
the database. This would greatly reduce the size of the database.
Also can a fulltext index be used on a column in a partitioned table. If so,
is this a 2005 or 2008 feature. Does anything special need to be done to the
partition function to handle the fulltext index?
"Simon Sabin" wrote:
> Hello Mike C#,
>
> See my series here http://sqlblogcasts.com/blogs/simons/archive/2008/02/20/SQL-Server-200...-iFTS-N
>
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>
> > "Jean-Pierre Riehl" wrote in message
> >
> >
> >> Hi,
> >>
> >> Yes, that is a major issue to integrate full-text engine into SQL
> >> Server. One of the side effects is performance improvement since
> >> full-text querying is included as operators in Query Execution Plan.
> >>
> >> Here are some improvements announced (i'm waiting for next CTP to
> >> test it)
> >> :
> >> -40 new languages
> >> -Noise words management with T-SQL (CREATE FULLTEXT STOPLITS
> >> -Thesaurus stored in system table and instance-scoped
> >> -indexed keywords querying
> >> -full-text parser querying
> > You can create fulltext stoplists in the current CTP. You can also
> > use new DMV functions to see how your full-text queries are parsed and
> > to view full-text index keyword entries in the current CTP. The
> > thesaurus is currently still stored in the file system on this CTP.
> >
>
>
> >> Stay informed about: SQL 2008 Full text indexing