If you already know about Automatic Soft-NUMA in SQL Server 2016, then you probably already read the blog post SQL 2016 – It Just Runs Faster: Automatic Soft NUMA by Robert Dorr, who makes up one half of “the Bobs” that run the BobSQL blog. The other Bob, Bob Ward (@bobwardms), followed that up with How It Works (It Just Runs Faster): Auto Soft NUMA…. Lots of great info there. So having read up on automatic soft-NUMA, I was eager

Welcome to T-SQL Tuesday #85 being hosted this month by Kenneth Fisher (blog|@SQLStudent144). This month’s topic is “Backup and Recovery”. This is one of my favorite topics, so the hard part was narrowing down what I want to cover .. as you can probably tell by me doing a second post for this month. I call this one T-SQL Tuesday #85 Part Deux. If you would like to participate in this month’s blog party, go to Kenneth’s invitational blog post:

Welcome to T-SQL Tuesday #85 being hosted this month by Kenneth Fisher (blog|@SQLStudent144). This month’s topic is “Backup and Recovery”. This is one of my favorite topics, so the hard part was narrowing down what I want to cover. If you would like to participate in this month’s blog party, go to Kenneth’s invitational blog post: T-SQL Tuesday #85: Backup and Recovery. NoRecovery Many of you already familiar with the NORECOVERY option for performing restores to allow you to continue

It’s time for T-SQL Tuesday again, and this month’s host is fellow Certified Master and Data Platform MVP Jason Brimhall (Blog|@sqlrnnr). Jason has challenged us to spend some time sharpening a skill and then blog about it. For my participation, I found myself needing to get reacquainted with a third-party backup software that I had not used in many years, LiteSpeed for SQL Server by Dell. I worked with LiteSpeed extensively many years ago when I was a DBA at

On one of my SQL Server instances, I see a lot of these infinite recompile messages in the SQL log. Sounds bad, but they never lined up with any detected errors or failures, and I always seemed to have more important things to focus on so I let it slide. Well, today was a slow day — being the Friday before a holiday weekend — so I decided to investigate. The error messages, error #2814, all look like the below:

Recently, I needed a query to identify tables that developers had create as point-in-time backups of tables that were never used again (turns out, there’s quite a lot of them in this database). They are characterized by having _bak or _ appended to the end of them. I wanted to provide a list of the tables to the development team and give them the opportunity to say that any of the tables should not be deleted. I wanted to provide,

Recently, I wrote a maintenance script to check every table in every database on our servers at work nightly and email a report of identity columns that are approaching the limits of their data type. The minimum and maximum values for most numerical data types are documented in Books online, but for decimal/numeric data types it is not documented and varies based on the values provided for the precision and scale. Most people know that precision is the total number

Thanks to everybody that participated in this month’s T-SQL Tuesday. A big thanks to everyone who wrote a participating blog post, and a really huge thanks to everyone who read the posts shared by this month’s participants. If you follow one of the links on this round-up page, I will kindly ask that you leave a comment on a blog post that you read if it teaches you something, gives you a new perspective, or makes you think. A blog

Welcome to my contribution for T-SQL Tuesday 74 being hosted by me. So special thanks to me for hosting it. Good job me, I’ll buy me a beer next time I see me to thank me properly. But enough about me, my post is about using Query Store in SQL Server 2016 to identify queries or plans that have changed. Visit the blog party page to take part in this month’s T-SQL Tuesday event or to read other blog posts

It’s time again for that T-SQL blog party T-SQL Tuesday, and this month’s host is Mike Donnelly (blog|@SQLMD). If you want to join in the blog party, take a look at Mike’s announcement for an explanation of the topic and rules for participating: T-SQL Tuesday #065 – Teach Something New. My contribution this week is about overcoming the variable limitations of SQLCmd mode. Most people know what SQLCmd is, the command line SQL client utility for running T-SQL, or perhaps