SQL Server Fulltext resource & FTDATA location

SQL Server Fulltext resource & FTDATA location

Post by quackhandl » Tue, 05 Jun 2007 21:04:18


Win2003 Server SP1 (with Windows Cluster Services Installed)
SQL 2000 Ent SP4

I am trying to perform a data migration database that contains a
fulltext catalog on one table. The migration is from a single
standalone server to a 2 node active/passive cluster. By mistake the
catalog was built on the drive with the SQL installation eg - T:
\Program Files\Microsoft SQL Server\MSSQL\FTDATA\ However due to
space requirements, we want to put the catalog on a different (and
larger) drive Y:\FTDATA

1) Is the above possible as I have read BOL and it states that "Full
Text Catalogs must be created on a local hard drive associated with an
instance of Microsoft SQL Server"?

In the end I removed the catalog from T:\ drive and reset everything,
however now then I received the following error: The Full Text Catalog
'' is missing. Please use, etc, etc" I decided to tweak the registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\ (I did backup
first) to remove all traces of the catalog on the T:\ drive and point
any future catalogs to Y:\FTDATA however when I restarted the search
service, the SQL Server FullText Resource has now failed and refuses
to come back online. I have been here: http://www.yqcomputer.com/
but unfortunately no luck.

2) what do I have to do to get the resource back online?

3) Do I have to change the registry on both nodes?

4) Help!!!!!!!!!!!!!

Anyone out there with any ideas?



1. Upsize to sql server overrides sql server default location--wh

2. SQl server at each location or centralised SQL server

Hi All

I need advice on how to implement a solution for a customer who has an
Outlet in every state in Australia (7)

My application is a POS program for sales of products for a company which
sells newspapers

I am using SQL server 2005 express as the database

Should each location have its own SQl server database and update Head office
by polling OR

Should each location connect to the 1 Head office database via VPN, with a
failover to their local SQL server if the connection is down

I have been working on the polling method for a while, but find it very
difficult to get a satisfactory updating procedure to head Office,
especially regarding update conflicts and successful synchronising in

I am beginning to think the centralised database option to be most reliable

Can anybody point me to some sites with info on Best practices, or give me
suggestions from their experiences etc


3. Upsize to sql server overrides sql server default location--why?

4. Missing "SQL Server" & SQL "Server Agent" Resource after installat

5. SQL server 2005 fulltext index

6. SQL Server 2005 - FullText Search

7. SQL Server Agent and Fulltext Services Autostart?

8. SQL Server Fulltext>: 80040154 - Class not registered

9. "weight" failing in fulltext search in Sql-Server EE

10. sql server 2005: can documents and text be together in the fulltext world ?

11. problem in fulltext search in MS SQL Server

12. SQL Server 2005 and pdf fulltext search

13. FullText Search & SQL Server Express Edition

14. SQL SERVER 2008 Create FullText stoplist table Failed

15. sql server fulltext query results