Post reply

MY WINDOWS TEAM GOING TO CHANGE THE DOMAIN NAME

  • December 30, 2013 at 5:39 am

    #287766

    HI,

    I HAVE A DOUBT MY AD AND WINDOWS TEAM GOING TO CHANGE THE DOMAIN .IS THERE ANY PROBLEM GOT AFFECTED MY SQL SERVER ALREADY PRESENT

  • December 30, 2013 at 9:35 am

    #1676418

    Hi,

    Obviously each SQL Server could differ with regards to what is affected by the server's domain changing but here are a few things to look out for, particularly if the old domain is being decommissioned or moved out of scope:

    SQL Server Service logins (SQL Server, SQL Agent etc...)

    Windows logins used to access DBs

    Check your SPNs (using setspn if required)

    Note that this is not an exhaustive list, these are the items I check when the server is migrating domain.

    If you have a test environment, I'd practice on that first, if not - try installing SQL Express on a non production machine and change the domain on that and see what happens. At the very least the latter will give you some idea of how SQL Server will react in your domain environment when the domain changes.

    When changing SQL Server Service logins, make sure you use SQL Server configuration manager.

    Good luck.

  • December 31, 2013 at 1:58 am

    #1676536

    can you send me step by testing prodecure what we looking for

  • December 31, 2013 at 1:54 pm

    #1676677

    pradeep.k 50453 (12/31/2013)

    can you send me step by testing prodecure what we looking for

    You should be able to come up with your own testing procedure after reading this thread:

    http://dba.stackexchange.com/questions/37583/moving-sql-server-to-different-domain

  • January 1, 2014 at 2:03 am

    #1676711

    we will work wth the following in our test environment ,thank you

  • January 2, 2014 at 6:15 am

    #1676867

    Also do not forget other applications that use your SQL server. You may have web applications for example that will also be impacted.

    As mentioned earlier, some of this may not be apparent until SID history is turned off.

  • January 2, 2014 at 6:46 am

    #1676881

    Are any of the SQL Servers Clustered? If so... that is a much bigger process. I believe that Win2008/SQL2008 clusters cannot be moved to a different domain due to the internal IP addresses that cannot be changed for the cluster.

  • January 2, 2014 at 6:49 am

    #1676883

    no sql server not in clustered ..

  • January 2, 2014 at 6:52 am

    #1676886

    If you have a domain ID that runs the SQL Server service that ID will need to be setup in the new domain... plus that ID will need to be granted 'sa' rights within SQL Server before the cutover. Otherwise SQL Server will not start.

  • January 2, 2014 at 3:04 pm

    #1677065

    Markus (1/2/2014)

    If you have a domain ID that runs the SQL Server service that ID will need to be setup in the new domain... plus that ID will need to be granted 'sa' rights within SQL Server before the cutover. Otherwise SQL Server will not start.

    Ideally, you would create new service accounts in the new domain. If the domains are trusted you can then migrate SQL Server to the new domain service accounts before the server itself is moved.

    If you installed with Service SID's (recommended for 2008 and above), then all you have to do is change the service start up account (use configuration manager for that change). The service SID already has all the permissions it needs, access to the appropriate folders, etc... If you have any agent jobs that require network access - make sure the new service account has the same privileges.

    There shouldn't be any need to grant anything in SQL Server itself, as the service account is not actually added to SQL Server. The service SID is added and that is what has access. If your service account was manually added - then you do need to add the new service account and match the permissions.

    Note: there is NO requirement for your service accounts to have sysadmin rights directly. They should only be granted the minimum access needed to perform whatever tasks are required. SSIS packages is a good example of where you need to add the service account - and grant execute rights to the stored procedures the SSIS packages will execute.

    Jeffrey Williams
    Problems are opportunities brilliantly disguised as insurmountable obstacles.

    How to post questions to get better answers faster
    Managing Transaction Logs

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply