Unfortunately we discovered a small bug in 1.3, the Database ownership module default warning level was not showing a yellow advisory condition when using the Inspector default warning level (NULL), we have now updated Git with the latest revision. If you would rather not re install 1.3 again you can workaround the issue by running... Continue Reading →
Inspector V1.3 is now available on GitHub. We have updated the sample report for you to play with which includes the new informational section added in this build. We updated our getting started guide. We know some of you really hate linked servers so we have been working on a powershell collection which will allow... Continue Reading →
During a recent DR scenario I came across a slight misinterpretation in how availability groups with replicas in synchronous commit behave. How An Availability Group With A Synchronous Secondary Should Behave Under Normal Circumstances Normally, if we've got a secondary replica in synchronous commit mode, our primary can't commit any transactions until that transaction has... Continue Reading →
Firstly, all of us at SQL Undercover would like to wish you a very Happy New Year and all the best for 2019. To sign off for the year, here's a quick run down of the most popular posts from SQL Undercover in 2018. Thanks to everyone who's supported us over the last 12 months.... Continue Reading →
There are times when we need to compare two tables and figure out if the data matches. I often see a number of ways of doing this suggested, most are quite slow and inefficient. I'd quite like to share a quick and slightly dirty way of doing this using the CHECKSUM and CHECKSUM_AGG functions. CHECKSUM()Just... Continue Reading →
What's the deal with logins and availability groups? I'm sure that we all, when creating a login that accesses a database that happens to be part of an availability group, diligently go and create that login on all secondary replicas, don't we?! Of course, when that AG fails over to another replica, we want to... Continue Reading →
For some reason I have always written my Case statements using the following logic: It wasn't until recently that I noticed that there is another syntax that can be used with the CASE expression, the interesting part about this other form is that it is rather aesthetically pleasing when dealing with multiple WHEN clauses... Continue Reading →
This is going to be a quick look at an issue that we recently encountered, I'm not going to go in depth into spinlocks and what they are (perhaps that could be the subject of a future post). We were enjoying a nice peaceful afternoon when we hear panicked shouting that a SQL Server had... Continue Reading →
So, this month's T-SQL Tuesday topic is to think about a non-SQL Server technology that we want to learn. For me, I'm going to pick machine learning. As a DBA, I've always looked at machine learning as a thing for the BI guys. I'm a DBA after all why do I care about that? Well,... Continue Reading →
