A client’s full backup always failed at 60%: backup detected log corruption, context is bad middle sector. Here is what the ERRORLOG showed and how we fixed it.
SQL SERVER – Mirroring Error 1456 – The ALTER DATABASE Command Could not be Sent to the Remote Server Instance
Adding a new witness server after a disaster failed with database mirroring error 1456. Here is one possible cause and what to check.
Collecting Server Hardware Facts Before a Tuning Session
Capture server hardware facts from SQL Server views, keep an inventory, and distinguish visible resources from workload sizing evidence.
SQL SERVER – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
A client used AlwaysOn automatic seeding for a huge database, but it stayed in Restoring state on the secondary. Here is the reason we found.
Which is Better for Performance – SELECT or SET? – Interview Question of the Week #166
Which is Better for Performance, SELECT or SET? In a loop, one SELECT that assigns several variables beats separate SET statements. Here is why.
QL SERVER – Unable to Create Listener: Msg 41009 – The Windows Server Failover Clustering (WSFC) Resource Control API Returned Error Code 5057
Creating an AG listener failed with Msg 41009: the Windows Server Failover Clustering (WSFC) resource control API returned error 5057. Here is the fix.
High CPU Consumption in SQL Server: Where to Look First
High CPU consumption in SQL Server comes from a handful of causes, and a short checklist finds them in order. This post reads the scheduler queue, ranks cached queries by CPU, and checks the Common Criteria Compliance setting that caused a known CPU problem after upgrades. It ends with the update that fixed that case and the questions to ask before you add cores.