This month’s T-SQL Tuesday is brought to you by Jens Bestergaard - the subject is Essential SQL Server tools, the original invitation can be found here. Here is how my day of using SQL tools went: It all started at 00:00 this morning with planned maintenance, I was adding a bunch of Clustered indexes... Continue Reading →
We all go to great lengths to make sure that our databases are secure (or at least I really hope that we do), we make sure that only authorised users have access and then only to the databases and levels that they need. We're careful that all our passwords conform to crazy complexity rules. We're... Continue Reading →
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 →
Here's a strange one that I've recently come across. I had a customer report that their log shipping restore jobs were chock a block of errors. Now, the logs seem to have been restoring just fine but before every restore attempt, the job is reporting the error, Error: Failed to update database "DATABASE NAME" because... Continue Reading →
Here is a quick guide to getting started with the SQLUndercover Inspector. Pre-requisites: SQL 2012 or higher SQL Server Agent A database to store the the data collected by the agent jobs (this can be one you use for your other DBA needs it doesn't have to be a dedicated database) Optional: For instances with... Continue Reading →
