GP v6 SQL 7 move to SQL 2000 1

[marsmanhunter]

I have moved GP v6.0 from SQL Server 7.0 on NT to SQL Server 2000 on a Win 2003 server for an anticipated server upgrade. My tests with GP appear to be okay, but I am concerned that GP might access SQL Server system tables, which would change from SQL Server 7.0 to SQL Server 2000. Does anyone know if this is an issue or not? Has anyone successfully made a similar move?

Thanks for your help!

 

[jazgeek]

I've done this 3 times without any difficulty.

make sure your sort order is matching to the old sql server or you may run into some problems there.

-----------
and they wonder why they call it Great Pains!

jaz

 

[barbola]

I just found a problem from over a year ago when we changed servers. Our SQL Agent jobs didn't get copied onto the new server, and our PJOURNALS table in one company ended up with over 900,000 records in it.

Just a heads up, although we did this with inexperienced staff.

 

[RobertC22]

Great Plains 6.0 is aware of the difference between system tables version 7.0 and 2000. GP 6.0 refers to system stored procedures and system tables using the name that is common to both SQL7 and 2000 (even if SQL2000 BOL says its supported for backward compatibility only).

Great Plains 5.5 is not, and so will not work correctly in SQL 2000.

As mentioned by jazgeek, the Sort Order (known as Collation name in SQL 2000 ) is critical!

And finally, I have completed this move on many occassions.

You may also need to run the sql scripts locks.sql found in .\sql\utilities\ subfolder. Run this script on the SQL server, to create the required stored procs in the Master database as needed by Great Plains. (See KB 860450)
I know version 8.0 onwards will automatically create these if not present when you logon as 'sa'.

------
Robert