Question: What Part of the SQLDump Suggest Database Corruption?
SQL SERVER – Why Suddenly DBCC CHECKDB Running Very Slow?
Recently during Comprehensive Database Performance Health Check, I was asked a fascinating question. They wanted to know why suddenly their DBCC CHECKDB process started to run very very slow.
SQL SERVER – Too many dumps generated. CPerIndexMetaQS::ErrorAbort – Index Corruption
I always try to share my knowledge and learning from a client engagement. This helps me in remembering the steps I took to reach to the solution. It also helps my blog readers to follow the same steps and fix their problem rather than waiting for some expert to fix it. So you see, this is a WIN-WIN situation for both of us. Let us learn in this blog post how to fix index corruption.
SQL SERVER – Alternative to DBCC INPUTBUFFER – sys.dm_exec_input_buffer
DBCC INPUTBUFFER has been one of the most popular commands to display the last statement sent from a client to an instance of Microsoft SQL Server. We all have been using it for quite a while. However, this DBCC command showed very little information and DBA always wanted to see more details. In SQL Server 2016 we have a new Dynamic Management Function (DMV) sys.dm_exec_input_buffer which provides many additional details as well.