Server move

[Andyleates]

Hi all

I have a SQL 2005 server that belongs to a sister company, which we are closing down.

This server needs to be moved into my AD domain now. What are the consequences as far as SQL goes, and does anyone have any tips?

Thanks

Andy

Andy Leates MCSE CCNA MCP+I

 

[ClaireHCM]

Here are the different approachs you can take.
1. You can use backup restore to move the databases from one server to other. -- No downtime

2. Use detach and attach --Downtime required

3. Take DB offline and copy the database files over to the other server, once copy completed, bring first server DB online, then attach the DB files in second server. --downtime required.

 

[Andyleates]

Thanks, but I am not actually moving the database to a new server, it's the same server, just in a different domain...

Andy Leates MCSE CCNA MCP+I

 

[ClaireHCM]

Hmm....In that case, I am not sure. My suggestion is to work with Sys administrator or network admin for the server domain move.

 

[onpnt]

I just did this and the only thing that needed to be addressed was the name resolving correctly for the server (it was a default) and security of your login accounts of course will need to be slowly moved over. If you have well rounded systems administrators they should be able to manage your groups accurately so you can leave the security accounts as is while slowly migrating them to make sure nothing gets hacked up. Otherwise you'll need to move them all at once to the new domain. If the server was setup well you should only have to worry about windows groups and not user accounts. And if it is sql authentication no problems or changes at all.

Other than that you shouldn't have any problems.

That is of course unless third party applications utilizing the instance as a data stored have some funky things going on. In that case I would call your vendors of those applications for recommendations.



[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[mrdenny]

Make sure that you know the sa password before you do this. If you don't and the server is locked down you won't be able to get into the SQL Server when it comes up on the new domain as no accounts on the new domain will have rights.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[SQLBill]

Make sure all the user logins are changed to the new domain. Also, check the front end applications. We had some front end connections that used the full string....

servername.domain.com

Luckily, we thought of that in advance and our web frontend people were prepared for it and fixed their config files to work with the new domain.

-SQLBill

Posting advice: FAQ481-4875