What’s the issue?
The Dedicated Administrator Connection (DAC) is a special diagnostic connection in SQL Server that uses a reserved scheduler and memory resources, allowing a sysadmin to connect even when the instance is unresponsive to normal connections.By default, the DAC is enabled but is only available locally from the SQL Server host itself. The remote DAC, which allows administrators to connect to the DAC from another machine over the network, is disabled by default and must be enabled explicitly.
Why is this a problem?
When SQL Server is in distress (CPU saturated, worker threads exhausted, blocking chains preventing new connections), normal connection attempts will fail or hang, leaving administrators unable to investigate or resolve the issue.If the remote DAC is disabled, the only way to use the DAC is to log onto the SQL Server host itself via RDP or console access, which is often inconvenient or impossible during an incident, particularly outside business hours, in cloud environments, or on servers without remote console access. By the time someone can physically reach the server or establish RDP, the issue may have escalated to a full outage that requires a service restart, with all the associated impact and lost diagnostic information that a restart implies.
What should you do about this?
Check the current state by running EXEC sp_configure ‘remote admin connections’;. A run_value of 0 means remote DAC is disabled. Enable it with EXEC sp_configure ‘remote admin connections’, 1; RECONFIGURE;. The change takes effect immediately and does not require a restart.Verify the DAC port (typically dynamically assigned and visible in the SQL Server error log at startup) and ensure firewall rules permit DAC traffic from administrative workstations or jump hosts, restricted to those specific sources rather than open broadly. Document the connection method for the team, since connecting to the DAC requires specifying the ADMIN: prefix in the server name when using SQLCMD or SSMS (for example, ADMIN:ServerName,PortNumber).
Test the connection from your normal administrative workstation under non emergency conditions so the procedure is familiar before it is needed. Add this setting to your standard server build checklist so new instances ship with remote DAC enabled.