Deployed 2-node SQL Server Availability Group with automatic failover and synchronous replication using SQL Server Always On

What if you could measure your SQL Server health with a single score? 🤔 In most production environments, we check performance issues separatelyblocking, slow queries, CPU usage, job failures… But there’s no simple way to understand overall database health at a glance. So I built this 👇 👉 SQL Server Performance Score System 🔗 https://lnkd.in/eCh7cb7B

TempDB ate your disk and your manager is breathing down your neck. Here's how to wrestle it back without taking SQL Server offline. https://lnkd.in/gh4jWE5B #SQLServer

A little more transparency is good – but fixing the bug would be even more desirable? Or will this issue be handled as "by design"? But at least, thanks for documenting it.

Are you, or other users, experiencing performance drops at the same time every day? It is a far too common of a problem in many SQL Server environments, without anyone actually understanding WHY it happens in the first place. But there are a few usual suspects to keep a lookout for. Swipe through to see which ones they are. #SQLserver #databaseperformance

Say it with me… “Least privileges”. We don’t use the ##MS_DatabaseManager## role (or its twin db_creator), mostly because, well… …because I hold an unpopular opinion: Only DBAs should be able to create, much less assign ownership to, a database. I’ve got 99 problems, but this ain’t one. #SQL #SQLServer #DataArchitecture #DataSecurity

SQL Server upgrades are expected to improve performance. In this case, a major SQL Server upgrade introduced severe performance degradation, impacting throughput and putting the program at risk. Internal teams were also constrained by limited access to vendor-owned code. This case study shows how a structured performance engineering approach identified and resolved bottlenecks across the database environment. The upgrade was completed successfully, improving reliability, increasing transaction throughput, and delivering measurable commercial impact. Explore how the approach was applied: https://bit.ly/4sJhDVV #SQLServer #SQLServerUpgrade #DatabasePerformance #PerformanceTuning #DataPlatforms #BlueCrystalSolutions

In SQL Server, the concepts of Buffer Pool, Dirty Pages, Lazy Writer, and Checkpoint are tightly connected and form the foundation of how the database engine manages memory, disk I/O, and recovery.

When users say, “SQL Server is slow”, they’re not talking about wait stats, memory grants, or disk latency. They’re talking about the symptoms of what is causing the server to run slow. As DBAs and architects, our job is to translate those symptoms into evidence, and one of the ways to do that is by choosing the right Performance Monitor counters. #SQLServer

Don’t let blocking or deadlocks slow your SQL Server. Our video explains their differences and how to troubleshoot them. Watch now: https://lnkd.in/gxzCgwKp https://lnkd.in/gxzCgwKp

Why is my SQL Server stuck? Ever had your database "hang" for no reason? No errors, just infinite loading? The cause is often a Forgotten Transaction. Someone started a task but never finished it (No Commit or Rollback). This locks the data and blocks everyone else. The Fix: Use this simple query to find the Block How it helps: ✅ Who: Shows the user name holding the lock. ✅ When: Shows exactly when they started. ✅ Action: Gives you the session_id so you can stop the process and free the database.