Skip to main content

Enabling Remote Access to the Dedicated Admin Connection

Recently I was running a health check on one of my clients SQL Servers and I noticed that access to the dedicated admin account was disabled. They would not be able to connect to the Dedicated Admin Account (DAC) remotely.  It is generally good practice to enable remote admin connections. If you have a server that is under so much load that all the resources are used up. SQL Server always allows saves enough resources for one single session to connect. You can’t use object explorer so you will be limited to one Query Window or connect through SQLCMD.  Enabling this would allow my clients in-house DBAs to connect to the DAC when you are not physically connected to the SQL Server in question should the need arise.

This is a pretty useful feature and whilst you can use a local DAC connection by default. That is, when you are connected locally to the server in question, you can connect using the DAC. If you want to connect remotely you need enable the ‘remote admin connections’ server options.

You can check is the ‘remote admin connections’ is enabled by running the following query

SELECT *
FROM sys.configurations

-->
where name like 'remote admin connections'

A value_in_use of 0 indicates local connections. A value of 1 means that remote connections are enabled


You can change the option if you need by using SP_CONFIGURE and the code below

Use master
GO
sp_configure 'remote admin connections', 1
GO
RECONFIGURE

-->
GO

Enabling the DAC can be a lifesaver if you get a rogue query chewing up all the resources on a server and it can be a good idea to enable it. I wrote a post over 6 years ago saying to connect to the DAC you can see the link to that below

Related Posts
Connecting using the DAC - http://www.gethynellis.com/2010/09/sql-server-dedicated-administrator.html



Comments

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

How to Setup Kerberos Correctly

David was in Copenhagen this weekend delivering his Kerberos talk Taming the Beast: Kerberos for the SQL DBA to SQL Saturday Denmark. I have had a quick chat with him via email since he got back and he said he had a great time. The event was very well attended with 280+ attendees and his talk was well attended.

I think David is planning submitting a few sessions to SQL Saturday events in Europe in the next few months so look out for him there and we'll keep you posted as to his whereabouts when schedules get finalised later in the year.

David has pre-recorded his Kerberos talk. You can watch on you tube and I have also embedded it in this post if you want to see what his kerberos talk  covers...



If we can help you with a SQL Sever problem visit our SQL Server Consulting page or contact us