Hello,
We've run upgrade advisor and fixed everything and we're ready to upgrade from sql 2k to sql 2k5. We did find a problem though. Our current sql2k has an instance name of "dbserver". The problem is that we wanted to put CRM 3.0 data on this instance as well, but I guess CRM 3.0 will only install based upon the default instance only. So here is my thoughts and was wondering if someone see any problems on this process.
1. Install another sql2k instance, using the default instance name this time, on the current w2k3 box which holds our current sql2k instance named "dbserver".
2. Once default instance is up and running, transfer over logins, operators.
3. Stop current live instance "dbserver"
4. Use new default sql2k instance and attach all databases from the stopped "dbserver" instance other than master, tempdb, model, msdb.
5. Run the upgrade on default instance, which now has all current databases associated to it, for sql2k5.
6. Uninstall "dbserver" instance.
Anyone see any problems on suggestions? Thanks in advance.
You approach will work but there is a quicker option you could consider. You could install a default instance of SQL Server 2005 and migrate your databases and logins directly over to that new instance instead of going through the intermediate SQL 2000 installation step.
Michelle
No comments:
Post a Comment