What are best practices/important steps when the Windows Server machine hosting SQL Server 2008 R2 is moved to another domain? What steps definitely/might need to be done for SQL Server before and after the new domain is joined?
Moving SQL Server to a Different Domain – Step-by-Step Guide
configurationsql serverwindows-server
Related Question
- Sql-server – Login to SQL Server 2008 R2 remotely
- Sql-server – I need the reason why we should not install SQL server on the domain controller
- Sql-server – Limiting Domain Admins permissions on a SQL Server
- Sql-server – Error when trying to install SQL Server 2012 Ent in to a Server Core 2008 VM
- MongoDB cannot be started after moving the server
- SQL Server 2008 – ‘The Computer Must Be Trusted for Delegation’ Error
- SQL Server Migration – Assign Failover Cluster and High Availability Always On to New Domain
Best Answer
What do you need to take into account when migrating SQL Server to another domain?
The steps below presume:
Steps:
A. Backup:
B. Services:
C. SA account:
D. Service Windows account:
E. Windows domain accounts used to login to SQL Server
F. IP Address: SQL Server (unless clustered) will use the new IP address
G. Firewall:
H. DNS entries:
I. Service Principle Names (SPNs). Some standalone (and all clustered) instances use SPNs.
J. Client Network Utility Alias.
K. Client application and service connection configuration:
L. Internal machine name.
AFTER: If the machine name is also changing, SQL Server's internal machine name entry may need to be udpated
sp_dropserver 'MyOldMachineName' go sp_addserver 'MyNewMachineName','local' go
M. Merge Replication - If merge replication is in use, it will also need to be reconfigured.
Attributions - some information added from these sources:
https://serverfault.com/questions/49681/change-ad-domain-membership-of-a-server-2008-running-ms-sql-08
http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/f3e8ff83-8fcd-4335-87fe-ea5641ae6b88