March 14, 2005 at 9:03 am
We are currently running several SQL Server 2000 member servers on a W2K3 domain with a trust to a second NT domain where there are several more SQL Server 2000 member servers. The first domain is soon to be scrapped and two new domains created in its place. I'm new to SQL Server and need to know the steps to follow in order to minimise downtime. Thank you.
March 14, 2005 at 11:22 am
We did several domain migrations and I had no problems with downtime.
There are some other problems to pay attention to:
1. Check everything that has Windows Integrated Authentication: logins, jobs, DTS packages, Enterprise Manager Registration, Startup Accounts.... Example: when the machine was moved from Domain1 to Domain2 the job that was running in the context of Domain1\User1 did not run anymore.
2. Check for names in the Connection Strings, ODBC Data Sources, Linked Servers, TCP/IP Properties\Suffixes, Client Network Utility Aliases etc. especially if you are running in the multi-domain environment. You may have fully qualified names like server1.domain1.companyname.com or accounts Domain1\account1 hardcoded
3. The opposite process: if you are going from 1 domain to 2 domains than the objects: server names, accounts that are not currently fully qualified (don't have fully qualified names) have to be referenced by their fully qualified names or have DNS aliases. Ask your network admin about DNS aliases.
Yelena
Regards,Yelena Varsha
March 15, 2005 at 6:49 am
Thank you Yelena - that's really helpful.
Cath
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply