Announcements
No record found.
Does anyone know of any document showing the steps to move GP 9 to a new server and upgrade to GP 10 at the same time?
*This post is locked for comments
Please look at TK 878449. I do many moves each year and these steps tell it all. Probably more than what is needed in most cases.
And personally, I would recommend splitting into two steps what you are trying to do. This gives you the latitude to confirm a server change before upgrading. Because doing both and getting problem afterwards will not be an easy troubleshooting situation.
My personal choice though.
I would agree. I normally move the data onto the new server first and make sure all works. Then I perform the upgrade on the new server. This way if anything goes wrong you still have the original copy working and users can just keep working until any issues are resolved.
This is an attempt to get around that Richard. I tried to move the data to a new server and it doesn't work well. Weird errors. I thought that maybe by combing the move(s), it might clear out its issues.
If you want my advice... Bad idea! Try fixing the errors after moving the data from one server to another before upgrading GP.
What kind of server move are you trying to do and to what GP version you want to move from GP9?
Simply switching servers will occasion its set of difficulties, even if simply going from same OS and SQL server version. Now if you're moving from Windows 2000 to 2008 and SQL 2000 to SQL 2008, there are a whole bunch of considerations to take into count before thinking of upgrading GP9 to GP 2010 sp1...
By the way, did you patch GP 9 before doing the upgrade to GP 2010? You need to be on 9.00.371 at the very least.
1. Both systems are running SQL Server 2000.
2. The new server is W2003, the old server is W2000.
3. Both systems are version 388
1) Capture the SQL logins
2) Capture and jobs that are running
3) Detach the databases
4) On New Server install GP, run utilties to create DYNAMICS database
5) Detach DYNAMICS database on new server and copy over detached databases from old server
6) Attach databases to new server
7) Run the scripts to create the SQL users from step 1
8) There are also some other scripts to runs since you are on SQL Server 2000.
That should get you moved to the new server. After the data is moved you can do the upgrade on the new server. I do not believe GP 2010 is compatible with SQL Server 2000 so GP 10 will be as far as you can go. Most of these steps are outlined in TK 878449.
When moving to a new server I normally restore the old version's dbs on the new server and then install the new version's GP client on the new server. So, I guess that makes me a follower of the 'move and upgrade' in one step method. I used to do it the other way, but then found I was just doing extra work by doing the upgrade on an old server.
Just be sure to get the upgrade path document to make sure you are going from and to the correct build numbers.
Also, your passwords will need to be reset on the new server.
Kind regards,
Leslie
Thanks all. Yes, I did find that the passwords needed to be created. I may try it again this weekend. I will uninstall the GP and delete the databases from SQL 2000 and start from scratch.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
