Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

My SQL Server 2008 R2 doesn't work after changing the MAXDOP parameter on instances.

I have 6 instances located on the same physical server and I changed MAXDOP from 1 to 2 on 5 instances. After that all these 5 instances don't work. After restart of the server any services don't start and I just see the error

The request failed or the service did not respond in a timely fashion. Consult the event log or other application error logs for details

In Event Viewer I didn't find anything useful, also error log wasn't updated when I tried to run instance.

Also I noticed a strange thing. When I open the Configuration Manager and open properties of instance, I don't see the fonts of parameter's name in Advanced tab. In another tabs everything is fine. The screen is attached. Does anybody faced the same problem?

I don't have any idea how repair this...

error

upd: By the way, i tried start sql server manually from command line with -f or -m parameter but nothing.. I just see empty error window

share|improve this question
What is the source of that error message? sqlservr.exe? – usr Nov 17 '12 at 14:14
1  
Did you try to run chkdsk? Especially on C:\ drive? I think you should check this also... – Boris Hristov Nov 18 '12 at 6:34
1  
What is your server configuration? Number of cores? Amount of RAM? Drive layout? (where are the MDF, LDF files located, where is MSSQL?) What eventlog entries did you have during the change of MAXDOP? – hot2use Nov 20 '12 at 8:35
Maxdop setting does not and will not make sql server not to start. There might be something else going on. Can you post a. Error log message b. Output of systeminfo. – Kin Mar 15 at 20:44

migrated from stackoverflow.com Nov 17 '12 at 23:56

1 Answer

I have never get this type of error but I want to suggest you about a recovery tool. In this situation you should try to use this tool, which is Kernel for SQL Recovery. Just try to use this, maybe you can solve your problem with this tool.

share|improve this answer
1  
Please provide detail about how to use that tool. And please state whether you are affiliated with the vendor in any way or not. – dezso Nov 20 '12 at 10:36

Your Answer

 
discard

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