We are currently running Dynamics GP 9.0 and SQL 2005, all on our Small Business Server 2003. I want to install Dynamics GP 10.0 server on a separate PC ( Windows Server 2003 standerd), but keep the SQL 2005 DB on the SBS. Goal here is to keep GP 10.0 server seperate from the SBS, SQL 2005. We want to keep the 9.0 up and running untill we are satisfied that this migration is a success. I would have to create a mirror of our current GP 9.0 database on the SQL 2005, and run the GB 10.0 utility to upgrade this newly mirrored GP 9.0 database to 10.0.
My question... is this possiple? Our current 9.0 database name is.... NAME The mirrored name will be... NAMEGP Will the DYNAMICS database need to be mirrored with a new name as well? If not, will the DYNAMICS database be effected during this NAMEGP database utility upgrade?
If you are not upgrading the current 9.0 product, I don't see why your solution wouldn't work. As long as you show the installation for 10.0 the SQL instance to use (or create new) then it shouldn't overwrite the 9.0 DB.
As always, a full backup of the DB should be done to be safe.
Sounds like upgrading the second instance of the main 9.0 database will work fine. But what I'm concerned about is the shared DYNAMICS database. Do you know if the DYNAMICS db will be effectected during this upgrade?
I've been told by others that there can be complications after you upgrade from 9 to 10. The method that I'm suggesting here (a test upgrade) only makes sence. All the bugs from Great Plains can be corrected without disruption of the company's service.
I hope you get a response soon from MS regarding this, we need to move forward with this upgrade soon.
Wow....I can't believe I'm getting no response at all from my contacts. Either my email is going into their junk folder or they are ignoring me. Either way, they are supposed to get back to me, so I'm a little disappointed.
I would say that if the Dynamics DB is local and you are installing the new version on a separate box then there isn't much that can happen to the old one. Other than that, you may want to either Google around or attempt to post this in another TA here that is more relevant.
As I said earlier, I'm no Dynamics specialist so I can only surmise by experience what might happen.
What would be the purpose for creating a mirrored database for testing. Why don't you just create a new SQL instance with a different name and copy the data from the original database into the test database. Run your Dynamics GP 10 utils and you should be good to go....... That way you leave your Database Name and Dynamics Database Name the same.
Thanks for getting back to us. Yes, I'll create a new instance of the companys version 9 database. Then run the utilities to upgrade this new instance. Then we will have a test dadabase for version 10. But, I will NOT create a new instance of the Dynamics database.
One question, will the utilities upgrade effect the Dynamics database? If the Dynamics database gets modified, will the version 9 workstations be locked out?
Yes the Upgrade will effect the Dynamics Database and you will not beable to log in with the version 9 workstations. Maybe I didn't explain it very good.
Create a whole new instance of a SQL Database. So you would have..... ORIGINAL = server_name/original instance name eg. gp_server/accounting and a copy COPY = server_name/new instance name eg. gp_server/test
Then copy you company database and your dynamics database into the new instance.
Then you can run through your GP utilities on your test database. Your GP10 utilities should never be run on your original database until you are completly ready to upgrade.
Make sure you only run GP 10 on your new test database, otherwise your version 9 workstations will not be able to log in.
