Today’s quick tip is for SQL Server Management Studio (SSMS). From time to time when I’m speaking I’ll get a question on how I pulled up help for a given DMV or table.
I figured it would be nice to start up a weekly chat while everyone is on lock down. If it goes well I’m up to make this a regular weekly or even a daily call.
I’ll start by saying that I swear I posted this at some point in the past but I don’t see it looking back at old posts. This is from Aug ‘19; though, I haven’t seen any release notes on corruption in Azure.
Let’s say you see a request to restore a database backup to an Azure Managed Instance. You do this task and then a few days later the team that asked for the restore says they are having problems connecting to the newly restored backup.
Some time back I wrote about the new data classification features in Azure and SQL Server Management Studio. If you’ve done quite a bit of work classifying your data using the extended properties, guess what?
Recently I ran into an error when trying to copy a small database bacpac into an Azure Managed Instance. It’s said that SSMS is able to do this task. Let’s see it in action.
I’ve created a sample ads extension that checks TSQL syntax in real-time for potential bad practice.
Have you ever needed to bulk edit a table from excel to change it into a group of insert statements or change multiple query lines?
Let’s talk about what XLOCK is supposed to do. XLOCK is a table hint that can be applied to a query to place an exclusive lock on the resources that the query accesses. This can be very dangerous because an exclusive lock on a table or partition could cause significant performance concerns.
If you’re a data professional or application developer chances are you’ve run into Microsoft SQL Server once or twice.
About a year ago I wrote about a new feature in SSMS that allows you to add a data classification to your columns. Today we’ll discuss what happens behind the scene and how to look at the classifications later.