Update SQL7 to SQL2000 for Great Plains 7.0 2

[barbola]

I'm planning on updating our SQL Server 7 to 2000 and then following with upgrading Great Plains version 6.0 to 7.0.

The Customer Source website has little information about the SQL udpate and MSDN site has a few more steps to follow.

Does anyone know if I need to run the stored procedures "sp_fulltext_catalog", "sp_fulltext_database", and "sp_updatestats" and against which databases do I need to run these? Or can I completely skip this because it's not in the Great Plains instructions.

Also, with SQL2000 replacing SQL7 it says we need to re-register the server. How do we do that?

Thanks!!



Thanks!
Barb E.

 

[Luvsql]

I've done this many times and using the upgrade wizard during the SQL 2000 install has worked everytime. I always get a good backup, then run the upgrade choosing to upgrade (instead of creating a named instance). You can then choose the new directories for your 2000 db and log files. The only issues I've had is if you use the SQL 2000 CD that you received from Microsoft Great Plains (original copy that has a flawed ini file). There is an issue where one of the steps fails, but it's a known issue with Microsoft, and you can download a file from their website to fix it (if you get the error, just do a KB search) then carry on with the upgrade process. Once it has been upgraded, launch GP and make sure everything is good with SQL before attempting to then upgrade to version 7.

 

[JamesLean]

The stored procs that you refer to are to do with the fact that after upgrading ANY SQL Server 7 DB to 2000 you need to rebuild any full-text catalogs and update any distribution statistics.

If you're not using full-text search then obviously you don't need to worry about that. I would update your statistics though as running SQL 2000 using SQL 7 stats will degrade performance.

--James

 

[barbola]

Thanks for the help! I found a maintenance tool in Great Plains to Recompile and Update Stats - I'm pretty sure now that is all I need to do. I'll use the sp_updatestats for my customized databases (non-Great Plains).

I will check to see which CD we have.

thanks again!
barb

Thanks!
Barb E.