It is not a normal behavior of SQL Server to generate minidumps. It is like a stress signal in SQL. When there is something “unexpected”, SQL Server kills the SPID and generates a dump. There are situations where SQL threads are not yielding (“Non-yielding Scheduler”, “Non-yielding IOCP Listener” or “Non-yielding Resource Monitor”) and there would be data needed to diagnose the problem later, so a dump is generated. These dumps are in the folder which has ERROLROG files. They can be triggered manually also using SQLDumper.exe for SQLDump.
SQL SERVER – SQLCMD Error – Failed to Load Resource File SQLCMD.rll
As you might know, SQLCMD is a command line utility which can be used to connect to SQL Server and run scripts/queries. While trying to run SQLCMD, I ran into below SQLCMD error.
SQL SERVER- Msg 22004, Level 16 – xp_readerrorlog – Failed to Open Loopback Connection. Please See Event Log for More Information
Many DBAs use sp_readerrorlog or xp_readerrorlog to read ERRORLOG files in SQL Server. SQL SERVER – Where is ERRORLOG? Various Ways to Find ERRORLOG Location
SQL SERVER – Msg 3013 – Cannot Create Worker Thread. BACKUP LOG is Terminating Abnormally
One of my clients sent email to know my quick suggestion on one of the error messages. Let us learn how to fix error related to worker thread.
Cannot create worker thread.
BACKUP LOG is terminating abnormally.
SQL SERVER – Msg 0, Level 11 – A Severe Error Occurred on the Current Command. The results, if Any, Should be Discarded
It’s always fun to fix something when there is no meaningful error message. As you can see in the blog title, message id = 0 and it doesn’t tell me how to fix the issue. Here is my checklist whenever someone reports below severe error:
SQL SERVER – SQL Express Installation Error – Wait on the Database Engine Recovery Handle Failed
Sometimes I get emails from software vendors who use SQL Server as a part of their product. One of such vendor contacted me for an issue where their software install was failing because SQL Express was not getting installed. It was failing with an error. The error message which they shared was “Wait on the Database Engine recovery handle failed”.
SQL SERVER – Adding New Database to AlwaysOn Replica is Slow
First, let me clarify, the words in the subject of this blog are the exact words used by my client and whatever you do and say but “customer is always right!”. Here is the complete story where we faced issue related to AlwaysOn Replica.