Steve,
We are going to test it out first on one of our development servers. The problem is, we do not have a test environment that exactly parallels our production environment, so even if things go well in test, I'm concerned there may be other issues we will encounter when moving to production. Maybe that is where we should focus first, trying to get dev to match production, although this is a large effort in our case. I have found some other resources also, but still nothing solid. I'll keep this post open for a while and see if any others respond. I'll post more informatoin when we start making the changes in development and see the results.
Thanks...
Main Topics
Browse All Topics





by: St3veMaxPosted on 2009-04-19 at 11:20:11ID: 24180023
From what I can read into your question and what I know; the issue with SQL is if you change the name of the server; not the domain; but that's an easy fix anyway.
I'm thinking that it would be a case of change the domain the server joins to in CompMgmt, reboot, fire up SQL and add the previous domain's users; but depending how quickly the migration is done; you may need to setup trusts between the two domains to allow users on the old domain access to your SQL Server...
Do you have a virtual environment you could play about with and hone the migration plan?