Post reply

Change of Domain on SQL Server machine

  • October 11, 2005 at 8:55 am

    #89475

    We have a server with a third party application + SQL database  that will be migrating to a new domain. The machine name will stay the same. The technical person of the integrator company, contracted to perform maintenance service on the software suggests the following:  Backup Sql db, migrate server, reinstall 3rd party application, set up application, reinstall sql server, install sql server service packs and restore database from the backup.

     I’m thinking… that is introducing other factors and/or the  reinstallation of  SQL server can bring more problems.

     Can we change the domain within the SQL server system tables to the new one? Or there is any other simple to have a successful migration?  Please advice.

  • October 11, 2005 at 11:22 am

    #596593

    I never had to reinstall SQL Server when changing domains.

    In my experience the following may happen when the machine name stays the same but domain changes:

    1. JOBS !!!! if the job was set by MyDomain1/user1 then this job will not run. Check all your jobs who is the user running them.

    2. All Windows Integrated authentication users: unless domain users with the same SID are created in the Domain2 (new, and I had a case like that) those logins have to be re-defined

    3. DTS JObs owners, Database owners... etc.

    4. FQDN for the server: it will be myserver.MyDomain2.mycompany.com, notify all your users and correct entries in Client Network Utility on the clients and connection strings

    I have to run to the meeting, may post something later. But all that I listed you will have to do anyway on the new installation too. You will have to do much more on the new installation then just fixing the existent logins

    Regards,Yelena Varsha

  • October 12, 2005 at 12:18 pm

    #596904

    Yelana is on track with all of the changes (here's probably a few more lurking, dependent on which features you use). After the prep-wprk when removing the computer from the old domain and going to a new domain a reboot will be needed. The you will have to reassign the service accounts as well. However, if the new domain 'trusts' the old domain you might not have to do a thing.

    One other important point --> contact the 'integrator company' and request that they get you another 'technical person' for your SQL Server related issues --> this guy sounds like he has the potential to be 'dangerous' ...

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • October 12, 2005 at 12:51 pm

    #596918

    No trust between the domains. Moving into Active directory(AD). Network Team will use the AD migration tool on another SQL server first. They are confident that the tool will take care of everything within SQL since both products are from Microsoft. Network team had created all accounts from old domain on the new domain.  I'm not sure that everything will work as smooth as they hope.

  • October 12, 2005 at 1:04 pm

    #596924

    I'm not so sure the AD migration tool will 'fix' Windows logins/groups within SQL Server ... but who knows ... any word on getting 'technical person'  ???

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • October 12, 2005 at 1:29 pm

    #596926

    I was involved once with Aelita Software in an AD migration and the tool actually performed very well. They were bought by Quest Software and I don't really know in what part of Quest Suit they were rebranded.

    The point is that usually for this migration that tool performs well if you do the homework correctly

    just my $0.02 

     


    * Noel

Viewing 6 posts - 1 through 5 (of 5 total)

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