June 22, 2016 at 9:53 pm
Hi all ,
I am wondering if I need to enable DAC ( Dedicated Access Connection ) in all production servers just in case Someday database engine is not responding to regular connections.
Should I enable it ? as default is Disable
Many thanks ..Any feedback are highly appreciated
June 22, 2016 at 11:24 pm
It is good practice to enable the Dedicated Admin Connection for Remote Admin Connections.
...
June 23, 2016 at 2:08 am
DAC is always enabled (and it's a good thing!). What you can disable is connecting to the DAC remotely. By default this is disabled, so the only option to connect to the DAC is from the machine where SQL Server runs.
Usually I don't even install client tools on my servers, so enabling remote DAC connections is a must for me. YMMV, but I find it safer to have DAC enabled remotely. DAC is not inherently less secure than any other regular connection, so there is no reason to disable it IMHO.
-- Gianluca Sartori
June 23, 2016 at 2:15 am
spaghettidba (6/23/2016)
DAC is always enabled (and it's a good thing!). What you can disable is connecting to the DAC remotely. By default this is disabled, so the only option to connect to the DAC is from the machine where SQL Server runs.Usually I don't even install client tools on my servers, so enabling remote DAC connections is a must for me. YMMV, but I find it safer to have DAC enabled remotely. DAC is not inherently less secure than any other regular connection, so there is no reason to disable it IMHO.
Correct and enabled for local connection. However Microsoft say; "On cluster configurations, the DAC will be off by default.", I have no way of verifying whether this is true or MS myth!
...
June 23, 2016 at 3:16 am
HappyGeek (6/23/2016)
However Microsoft say; "On cluster configurations, the DAC will be off by default.", I have no way of verifying whether this is true or MS myth!
True by implication, because the only thing that's enabled by default is local DAC, meaning a connection from the same name that the SQL instance is running. Since in a cluster that's a virtual name that isn't actually a machine (it's just the name of the SQL service), you can't use local DAC.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2016 at 11:02 am
GilaMonster (6/23/2016)
HappyGeek (6/23/2016)
However Microsoft say; "On cluster configurations, the DAC will be off by default.", I have no way of verifying whether this is true or MS myth!True by implication, because the only thing that's enabled by default is local DAC, meaning a connection from the same name that the SQL instance is running. Since in a cluster that's a virtual name that isn't actually a machine (it's just the name of the SQL service), you can't use local DAC.
Gail
thanks for this clarification, I have learnt something, I hope others including the OP have too.
...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply