This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 98%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
We are currently running Server 2019 as a domain controller that gives staff access to various shared files and folders, I have now been tasked with installing SQL Server 2019 I have read various forums that say it's not recommended to install SQL Server on a server that is set up as a domain controller.
Could anyone tell me what options there are available to me to solve this issue or would I need to purchase a separate server to run SQL Server on?
Thank you in advance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
That's correct, do not install SQL Server on a domain controller. The simplest solution may be to install the hyper-v roles (as only role) on host, then stand up two virtual machines. One for active directory domain services, and another for the database application.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hi,
Thank you for the quick reply, because I'm quite new to server administration could you recommend any websites that will give me a better idea of how to set up the configuration you suggested?
Kind regards,
Paul
Sure, you can follow along here.
https://www.nakivo.com/blog/how-to-install-hyper-v/
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hi @Paul Smith ,
For security reasons, we recommend that you do not install SQL Server on a domain controller. SQL Server Setup will not block installation on a computer that is a domain controller, but the following limitations apply:
• You cannot run SQL Server services on a domain controller under a local service account.
• After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
• After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
• SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
• SQL Server is not supported on a read-only domain controller. SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
• A SQL Server failover cluster instance is not supported in an environment where only a read-only domain controller is accessible.
Refer to MS document SQL Server 2019: Hardware and software requirements.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.
Additional see MS Support Installing SQL Server on a domain controller
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
It is not recommended for security reasons, but it is also not prevented. You can do it, but if someone exploits your SQL Server, they may gain access to your entire domain.
Hello,
Thank you for your question.
As a best Practice you should not install SQL on Domain controller as resource intensive and may create issue during migration or upgradation.
Hence keep both isolated to achieve best performance .
--If the reply is helpful, please Upvote and Accept as answer--