that would only work on a very small environment right? I've got 64 prod servers and nearly 200 total including non-prod, and the number of times in the last year I've had to do a desperate connection, whether RDP to the server, sqlcmd or whatever I can count on a couple of fingers.
In my shop, we consider DAC to be somewhat of a security risk, so it is disabled on all servers.
my network is reasonably reliable, so your mileage may vary, of course.
I'll admit that I don't have anywhere near that number of servers so, correct, it may not work for you.
You've piqued my curiosity a bit... if you have DAC disabled on all servers and something goes haywire on one of them, what do you do? Restart the SQL Service in the single user mode? That wouldn't be a bad idea but there could certainly be an important data loss the might rollback when the service restarts.
Disclaimer... I've never had to use DAC because of what I do with my smaller number of servers so I don't know all of it's capabilities in times of trouble.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)