If you have migrated your Database\Instance or if the drive holding the SQLdata has been decommissioned, then in those scenarios how do you move the SQL Full-text Filter Daemon Service Error Log (FDLAUNCHERRORLOG) from one location to another in SQL 2008.
“SQL Server Fulltext Filter Daemon Launcher” service will be up and running even though the FDLAUNCHERRORLOG is not getting generated.
Open registry editor:
Go to the location in “HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL10.<INSTANCEID>\Setup\SQLDataRoot” and change the value of SQLDataRoot to New location
Restart SQL full-text filter daemon launcher service from configuration manager.
IMPORTANT : This resolution contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Also, please test this in you Test environment before moving to the production server.
SE, Microsoft SQL Server.
Reviewed byAkbar Farishta & Sudarshan NarasimhanTechnical Lead, Microsoft SQL Server.
This solution does not work as claimed.
fdlauncherrorlog is not generated after change to new path.
Does not work as claimed.