March 18, 2009 at 11:31 am
Could you please tell me how can I test the full text search is working after the upgrade from sql 2000 to 2005.Like perform any queries something like that.
issue detected by upgrade adviser:
1. Upgrading will cause Full-Text Search to use instance-level, not global, word breakers and filters by default. After upgrading to SQL Server 2005; Full-Text Search will not use operating system components such as word breakers and filters by default. To allow the use of these operating system components, use the sp_fulltext_service stored procedure and set load_os_resources to 1
Corrective Action: After upgrading to SQL Server 2005, use the sp_fulltext_service to set the service property, load_os_resources, which allows the components to be loaded. You must run the following:
sp_fulltext_service 'load_os_resources', 1
March 18, 2009 at 11:48 am
In SQL Server 2000 Full Text is part of the Microsoft Search service which is a separate add on to SQL Server while in 2005 Full Text is part of the relational engine so you could do most things automatically.
I think you need to drop all existing Full Text indexes in a test box and upgrade to 2005 and add new SQL Server 2005 based Full Text indexes so your indexes will be native to 2005. The one requirement is 90 compatibility level in the database. This will also let you change Text/NText columns to Varchar(max)/Nvarchar(max).
Kind regards,
Gift Peddie
March 18, 2009 at 12:15 pm
Thanks,
I upgraed to sql server 2005 and did the corrective action for the full text search as upgrade adviser says. But now How can i make sure the full text seach is upgraed and working fine.Is there any queries we can run and make sure full text search is upgraed properly
March 18, 2009 at 12:22 pm
In 2000 you MUST manually populate the Catalogs to use Full Text that is not needed in 2005 so drop all your existing indexes before upgrading so you can use native Full Text indexes which you can create by right click on each table it is that easy just use the auto populate option.
I hope this is clear drop all 2000 Full Text indexes and you also need to make sure it is on in configuration manager.
Kind regards,
Gift Peddie
March 18, 2009 at 4:17 pm
Thanks Peddie,
I have checked the sql server 2000 in Enterprise manager->local(windows NT)->Support Services->Fulltext Search
There No items in the Fulltext Search. So its means that the sql server 2000 instance is not using Fulltext search service right?
please advice me
March 18, 2009 at 4:33 pm
I think some one skipped installing the separate Microsoft search service which actually runs Full Text in 2000, I don't have it running because I am running 2005/8 and Team Suites in one box. So check the article below and you could also right click and script the tables to see if the indexes are defined but not just running then drop all before moving to 2005.
If they are defined and not running please drop all before migration.
http://www.developer.com/db/article.php/3446891
Kind regards,
Gift Peddie
March 18, 2009 at 5:16 pm
Microsoft search hasbeen installed and running but it looks like we are not using this feature because there are NO fulltext itmes in Enterprise manager->local(windows NT)->Support Services->Fulltext Search
and also We have Remote servers in Security->Linked server->Remote Servers.So after the upgrade what shoud I do with these Remote Servers?
March 18, 2009 at 5:22 pm
That just means it is not populated because you must know the Catalog must be populated, so right click on each table and try to script it don't finish the operation just read the code if the indexes are there. If they are defined you need to drop them. You need to verify the indexes are not defined.
Kind regards,
Gift Peddie
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply