SQL Server on a domain controller

  • I heard a Microsoft speaker say that SQL Server should not be installed on a domain controller. Why is that?

  • Lots of reasons, such as security, server load, differeent administration tasks etc.

    It's not recommended to do this. But in a small organization with 10 PCs, why not? Budget has the last say.

     

  • I think that a lot of the reasoning stems from the fact that AD is a JET based database (IIRC) and Jet and SQL Server don't play too well on the same server (when they are both under load). They make the same recommendation against SQL and Exchange on the same server for a similar reason.

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

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