We have an email complaince application using a SQL 2005 server which is part of the domain. I want to build a new Windows 2008 / SQL 2008 server to replace the priginal SQL 2005.
Now to change the SQL connection within the application itself is a nightmare. With this I am curious if I could first, shut down the compliance application so no data is going to the current DBs. Next, backup these DBs and then shut down the
current SQL 2005 server.
Now, build on new hardware a Windows / SQL 2008 server. Go into AD and remove the original SQL2005 server and then simplay re add it using the same server name. Once this is done, join the new 2008 server to the domain using the old server name.
Reload SQL and create the original security accounts. Once this is done, create the databses and then restore using the backups.
Now the hope is that once this is all done, that I bring up the complaince application and it just connects to the new server and is happy as a clam.
Does this sound solid or am I looking to create other severe headaches by doing this and should just fight through the rebuilding SQL and then messing with the application to point it to the new server?
View Complete Post