moving SQL to a new domain

  • we're moving our SQL boxes soon, possibly to a new domain. during the move, we're also changing the ports that SQL communicates over for added security.

    i'm sure some of yall have done something like this... how did it go? what kinds of problems did you deal with? what kinds of advice can you offer?

  • A domain move is pretty easy. The Windows authentication users and service accounts are the only real problem. You may want to drop the logins first, they can be trouble if the don't exist on the new domain. If your domains have a trust relationship that works correctly, these will not even be much of an issue. If you change the server name in the process be sure to drop and add the local server so the global variable @@Servername takes the new name.

Viewing 2 posts - 1 through 1 (of 1 total)

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