J Voss,
Yes, the process to stop an 8 million row table FT Population will take some
time to stop ;-( as the "Microsoft Search" (mssearch.exe) service works
outside of SQL Server and has a number of async processes and cannot just
"stop on a dime" while FT Indexing multi-million row tables...
The quickest way to stop this process is just t to stop the "Microsoft
Search" (mssearch.exe) service and set it to manual. However, when you
re-start this service, the FT Population will re-start. To prevent this you
will need to "de-reference" the FT Catalog from the system tables as well as
remove the physical FT Catalog folder and files and remove the associated FT
Catalog registry keys. This not easy, not for the faint of heart, and
depending upon the SQL Server version you are using, I have a SQL code
script code that can make this process easier, if you're interested in this,
please email me directly.
Thanks,
John
[quoted text, click to view] "J Voss" <jvoss@discover-re.com> wrote in message
news:f249b1ad.0307310607.701d2333@posting.google.com...
> Hello,
>
> One of our people started to make a full text index on a table. The
> table has over 8 million records and would take about 3 days to
> complete. Our boss wants to stop the population process of the index
> but it does not appear to be stopping. They have issued the command
> from the SQL Admin console, right clicking on the table, and issueing
> the stop population command under the full text index options.
>
> Does the process to stop the population fo the index take hours and we
> are not being patient, or is there a better way to stop this.
>
> Thank you.
>
> J Voss