Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an application that uses SQL Server where I plan on deploying four instances to four different third-party dedicated hosting providers. The databases will replicate between each other. So, does each SQL Server reside in its own AD domain or should there be one AD domain regardless of location?

What are the pros and cons of each?

share|improve this question

SQL Server Replication uses local accounts rather than domain user accounts, so multiple domains really shouldn't pose a problem with respect to replication. Replication is designed to handle distributed clients and disparate environments relatively easily. I'm not a Windows domain genius, but I imagine that the work required to set up four member servers in the same domain across four different hosting providers will outweigh any managemability gain that you may stand to achieve.

share|improve this answer

I agree with Aaron. This is not a scenario for using AD infrastructure. I would go for standalone servers and using SQL authentication for connectivity between them.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.