February 10, 2010 at 10:32 am
We have a failing SQL2005 backup due to a corrupted Full-Text Search catalogue. I've tried rebuilding the catalog to no avail. Also tried partial backups in various flavors, but it keeps bombing even when specifying the file (unfortunately there is only a PRIMARY filegroup). This is a database that is part of a 3rd party app - the vendor is also investigating a solution - so there's not much I can do with the database itself. Nonetheless we haven't had a SQL backup for over a week now, it has some pretty critical data, and of course if we need to go to a backup our customer won't care if it's a 3rd party app or not. Any suggestions are greatly appreciated!
FYI, we are running SQL2005 with the current Service Pack on a 64-bit Windows 2003 Standard Server, and the physical server is a blade.
February 23, 2010 at 9:15 am
The problem is resolved - but Microsoft had to fix it. It had to do with the full-text catalog files from two different databases being in the same physical directory structure.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply