February 5, 2010 at 6:20 am
My employer has asked me to investigate 1) what happens, 2) known workarounds if needed, and 3) why not to do it, if they change our domain structure as follows:
Current domain : PROD.MYCOMPANY.COM
would become : PROD.ABCDE.COM
In other words, the MYCOMPANY domain must go away. I don't know if it is to simply be name-changed, or migrated from in a source-destination fashion.
I have 220 SQL servers hosting various applications. Over half are SQL 2000, and the rest are 2005. All are 32-bit. All servers are running Windows Server 2003, except a few old ones running Windows Server 2000. Some are SQL Express or MSDE.
Most are in the PROD domain, but a few are in other domains such as ITEMPROD.MYCOMPANY.COM . A few are clusters, which run on service accounts such as PROD\SqlAcct and PROD\SqlAgent. Others run on local accounts such as SERVERNAME\SqlAcct .
Would the clusters even start? For that matter, would any of them start?
Before anyone asks, "Why?", I've already asked, and apparently that answer is above my pay grade. However, I am allowed to pursue "why we shouldn't" to its fullest extent.
All informed opinions and especially any actual experience is most welcome.
Mike Hinds Lead Database Administrator1st Source BankMCP, MCTS
February 5, 2010 at 11:22 am
The only ramification I can think of is what you've already stated: all of the domain accounts that services run under will need to be changed. Not trivial; but not that hard either. Will require down time to change / reboot servers.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply