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 assume a state-of-the-art installation therefore nothing weird like DC and SQL-Server on the same machine. Think about an installation following the commendations of microsft and all the recommended settings on both servers in a windows 2008R2 domain with sql2008R2.

share|improve this question

closed as not a real question by Sven, gbn, jscott, Sam, Chris S Mar 7 '11 at 4:48

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Ideally, SQL Server should run on a dedicated server - no IIS, no DC, no other apps! This is primarily for security and performance reasons - memory, and disc IO particularly - but it also makes troubleshooting easier. If this is not about SQL Server Express, the licencing costs of SQL Server surely justify a dedicated box.

In clustered SQL Server environments, the installer prohibits SQL Server being installed on a box that is a DC.

See also:

share|improve this answer

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