Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


We have a SQL Server instance that has pegged out a few times in the last few weeks. No one has been able to figure out how to get on and kill processes so they have just been rebooting the server (eek!).

I ended up posting on here in an effort to get access to the server when it's in this state and was directed to the DAC. From what I've read this will allow me to connect the next time it gets pegged (untested as of yet), but I'm wondering if I will be able to do anything once I'm connected or will my queries just time out?

share|improve this question

you should be able to most stuff in theory as per this MS article: ; but I would imagine if the server isn't responding what so ever you still might run into issues. You should be able to at least run diagnostic commands (DMV's) and troubleshoot what is pegging your server.

share|improve this answer

One issue on a stressed SQL Server box is the memory pressure. Parts of the OS have been paged to disk and there isn't enough capacity to log onto the box.

I once read that you should enable this registry setting

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

It's still on technet for Windows Server 2003 but maybe it's complete horlicks now

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.