Here's a quickie that I've just stumbled across. I've just tried to initiate a manual failover of an availability group and received the following error. After a spot of head scratching and thinking that there was something wrong with my AG setup, it turns out that there's a bug in SSMS. I was running SSMS... Continue Reading →
Have you ever had an issue where TempDB was filling up on your secondary replicas? Do those secondaries happen to be read only replicas? When I have an issue with tempdb filling up the first thing that I usually do is try to figure out exactly what the space has been allocated to. You can... Continue Reading →
So for this month's TSQL Tuesday, Adam Mechanic has asked us to take a look into the future and think about what things might look like when TSQL Tuesday #200 comes around (apparently that'll be June 2026). So I thought I'd have a little bit of fun with this by going all sci-fi on you,... Continue Reading →
The other day I got thinking about what would happen if all databases on a single instance grew out, every single one of them! but not just once, what if they all grew out three, four or fives times overnight - what would things look like? Well I know the likelihood may be slim but... Continue Reading →
Here's a quick one for you. If you happen to be managing SQL Servers with a large number of databases and availability groups, it can sometimes be difficult to keep track of which database belongs to which availability group. sp_WhatsMyAG will tell you just that. You can either provide it with the database name and... Continue Reading →
SQL Undercover 