October 12, 2007 at 6:29 am
I am trying to find a SQL 2005 person to help with a problem.
Somehow, and I am not exactly sure how it happened, the
"sysft_ftcat_documentindex" SQL file for my Microsoft CRM data base got separated from the other SQL data base and log files (those reside on the server's C: drive). and was placed on a separate drive (drive F:) which failed. I did not have a backup of the F: drive.
If I run
EXEC sp_help_fulltext_catalogs
It returns:
F:\BACKUP\Program Files From C On 2007-02-03\Program Files\Microsoft SQL Server\MSSQL\FTDATA\ftcat_documentindex
How do I change that to:
C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\ftcat_documentindex
What are the steps (please be complete since I am a newbie) to get "sysft_ftcat_documentindex" recreated on the C:?
Thank you.
Rick Bellefond
October 12, 2007 at 8:55 am
October 12, 2007 at 10:17 am
TommyB (10/12/2007)
See MS KB240867 -
Tommy,
First of all thanks for your post.
Does that article pertain to SQL 2005.
Is that really the EASIEST way to change the path for a full text catalog and recreate it?
Thanks.
Rick Bellefond
October 12, 2007 at 10:27 am
My apologies - thought this was a 2000 post 🙂
Much easier in 2005 - see this article -
http://msdn2.microsoft.com/en-us/library/ms142511.aspx
Tommy
Follow @sqlscribeOctober 12, 2007 at 10:38 am
TommyB (10/12/2007)
My apologies - thought this was a 2000 post 🙂Much easier in 2005 - see this article -
Tommy,
I do NOT have a backup of the full text catalog to restore.
I need to create a new full text catalog for that data base and put it on the c drive.
Does that document cover that. Remember I am a SQL newbie.
Thanks
Rick Bellefond
October 12, 2007 at 10:49 am
You should just be able to drop the old one and create a new one; good step-by-step article w/ illustrations.
http://www.userscape.com/helpdesk/index.php?pg=kb.page&id=142
Tommy
Follow @sqlscribeOctober 12, 2007 at 11:42 am
TommyB (10/12/2007)
You should just be able to drop the old one and create a new one; good step-by-step article w/ illustrations.http://www.userscape.com/helpdesk/index.php?pg=kb.page&id=142
Tommy,
I think that we are starting to make some progress.
I followed those instructions from the document that you referenced and when I got to step 7 which is where I tell it that I want to create a new catalog and I give it a name. When I click the next button I get the following error "The wizard closed because it encountered the following error" "Could not load type 'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
Does that mean anything to you, it sure doesn't to me. 🙂
Do I need to drop or delete the current full text catalog before I can create a new one? If so, how do I do that since when I go to step 2 of that document you referenced "Define Full Text Index" is the only option that is not grayed out.
Thanks.
Rick Bellefond
Thanks
October 12, 2007 at 12:00 pm
Haven't seen that one. Are you running SP2? SMO issues within management studio can typically be alleviated by shutting down managment studio and reopening it. You can drop the old one, if my understanding is correct it is pretty well useless at this point anyway since the drive that supports it is no longer there. Good luck 🙂
Tommy
Follow @sqlscribeOctober 12, 2007 at 12:38 pm
TommyB (10/12/2007)
Haven't seen that one. Are you running SP2? SMO issues within management studio can typically be alleviated by shutting down managment studio and reopening it. You can drop the old one, if my understanding is correct it is pretty well useless at this point anyway since the drive that supports it is no longer there. Good luck 🙂
Tommy,
I tried exiting management studio and rerunning it and that did not make any difference.
If I execute
exec sp_help_fulltext_catalogs
It returns the reference to the drive that does not exist.
You're right, I think that my current full text catalog is useless!
How do I drop it?
I am not sure if I am running SP2 or not. How do I tell if I am running SP2?
Any other ideas? If not, is there another forum that you would suggest that I post to?
Thanks.
Rick Bellefond
October 12, 2007 at 12:48 pm
To drop the catalog (do this first) -
DROP FULLTEXT CATALOG catalog_name
Then try the steps above again.
To determine SP level -
SELECT SERVERPROPERTY('productversion'),
SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
Should be patched up to at least SP2 (http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en), the latest cumulative build for SP2 is out as well build 3186 (http://support.microsoft.com/kb/939537/en-us) which also has a bunch of fixes for full-text indexing.
Tommy
Follow @sqlscribeOctober 12, 2007 at 1:49 pm
TommyB (10/12/2007)
To drop the catalog (do this first) -DROP FULLTEXT CATALOG catalog_name
Then try the steps above again.
To determine SP level -
SELECT SERVERPROPERTY('productversion'),
SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
Should be patched up to at least SP2 (http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en), the latest cumulative build for SP2 is out as well build 3186 (http://support.microsoft.com/kb/939537/en-us) which also has a bunch of fixes for full-text indexing.
Tommy,
First of all I am running SQL 2005 SP1
I am using SQL 2005 with Microsoft CRM
Even with the full text catalog point to a non existant drive, Microsoft CRM seemed to run just fine.
The only issues that I really had was that I could not do a complete backup of Microsoft CRM (in SQL) and sometimes when I would reboot the server the METABASE data base would get wiped out and have to be restored.
I dropped that full text catalog and Microsoft CRM still seems to be running just fine.
When I tried to recreate a new full text index I am still getting the same error as before.
Is there any reason that I even need the documentindex full text catalog for Microsoft CRM? It seems like Microsoft CRM runs a bit faster without it.
What, if any, functionality do I lose if I don't have a full text catalog?
Thanks.
Rick Bellefond
October 14, 2007 at 12:04 pm
TommyB (10/12/2007)
To drop the catalog (do this first) -DROP FULLTEXT CATALOG catalog_name
Then try the steps above again.
To determine SP level -
SELECT SERVERPROPERTY('productversion'),
SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
Should be patched up to at least SP2 (http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en), the latest cumulative build for SP2 is out as well build 3186 (http://support.microsoft.com/kb/939537/en-us) which also has a bunch of fixes for full-text indexing.
Tommy,
I upgraded our SQL 2005 to SP2 and the process that you told me about to create Full Text Catalog that did not work with SP1 did work with SP2 installed.
Thanks for your help.
Rick Bellefond
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply