November 1, 2011 at 10:01 am
Hi All,
I have recently moved all of my databases (datafiles/logs/fulltext catalogs) in a clustered 2005 instance from one set of disks to another faster & bigger set of disks. I did this by taking each database offline in turn, running the “alter database db_name modify file(name=………………” and then bringing the database back online.
This all went perfectly fine without error. However, I have a query regarding the Fulltext catalogs, which I moved as part of doing this. Although, the Fulltext catalogs are being utilized from their new location (confirmed by querying sys.master_files and timestamps changing on individual files at the new location), I am still seeing a .idx file a .dat file being created/modified in the original directory location each day when my daily full backups run. If I query sys.fulltext_catalogs for each database with a fulltext catalog, then the path specified still refers to my old directory location.
So my question is, are there some additional steps I missed and need to do to stop anything writing to the old directory location? As we are looking at removing the old drives in the near future, so the old directory location will no longer exist, and I am concerned that this might cause an issue.
Dave
November 15, 2011 at 2:27 am
Would detaching and re-attaching the Database to the same (new) location likely to update the database metadata (i.e. sys.fulltext_catalogs) and correct the issue?
Dave
March 2, 2012 at 2:00 am
I currently have a similar problem. I had to move a full text catalog from a local disk to a mountpoint so that it can be backed up by SnapManager. The MOVE I did as explained in BOL, using ALTER DATABASE. It seems to be working fine, but SnapManager still thinks the file is located on C:. I traced what Snapmanager does and discoverd that the entry in sys.fulltext_catalogs still refers to the old location.
How do I fix this? Is it wise to do an update on this system table ? (I have not tried it yet and don't no if this is even possible!) Or is there another way to change the path in the system table?
March 3, 2012 at 4:17 am
In the end I reverted to dropping and recreating the Fulltext catalogs in the new location. Although it wasn't ideal, SQL Server then reports the locations correctly.
Dave
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply