One of the most popular questions I receive during my Comprehensive Database Performance Health Check is a difference between status in sp_who2 which discusses status as Running, Pending, Runnable, Suspended. Let us today understand them with regards to CPU.
SQL SERVER – Timeout Occurred While Waiting for Latch: Class FGCB_ADD_REMOVE
One of my clients contacted me to resolve an issue where they were seeing these errors few minutes after restarting SQL Server Service. In this blog, we would learn about how to fix error Timeout occurred while waiting for latch: class FGCB_ADD_REMOVE.
Azure – Which One to Get – Standard Disks or Premium Disks
During Comprehensive Database Performance Health Check, I have recently a very interesting experience with an Azure. In this blog post, we will discuss which disks are preferred for performance – Standard Disks or Premium Disks. Well, honestly my answer here is very simple Premium Disks. If you stop reading this blog post over here, I am totally fine as well.
SQL SERVER – Always On Availability Group Failover Generating Dump. Error: 17066: SQL Server Assertion: HadrFstrVnnUtils.cpp:479
One of my clients was using Always On availability group. They were having 3 nodes Always On AG setup. For simplicity, let’s call them Node1, Node2 and Node3. The first two nodes were in one subnet and node3 was in separate subnet. Let us learn about availability group failover.
SQL SERVER – Too Many SQLDump Files Consuming a Lot of Disk Space. What Should You Do?
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 – Errors When Disk Space is the Reason
In the past, I have written a number of blogs when it comes to working with errors pertinent to disk space running out. In this blog, I try to consolidate the common messages you are going to see in the Error logs when the database engine is not able to get the space that it needs from the disk subsystem. One of the common scenario’s where these are seen is while recovery operation (when SQL is restarted).
SQL SERVER – Backup Randomly Failing with Error 112 (There is not enough space on the disk.)
Solving puzzle is something everyone would love. IHere is the puzzle which they wanted me to solve for Error 112.