SQL Server 2019 brings a lot of great new features. Many are introduced by the IQP (Intelligent Query Processing) features and greatly improve query performance.
So you’ve decided to use Azure for your existing or new data project? This blog series is focused on choosing the right technology for your project. It’s tough right? So many options and so many variables. This post will focus more on the cost of choices.
Twenty something years ago when I started my SQL Server career there was an amazing tool called Query Analyzer. Honestly I’d say if Microsoft did nothing more than bring this tool back and call it Azure Data Studio I would have been excited and beyond happy.
Today is May the fourth and I’ll start by saying: Happy Star Wars day to all. Since it is May the fourth I figured a Star Wars themed post would be nice.
This tip comes from my DBA days working with SQL Agent Job schedules. If you’ve ever worked on a server where many people created job schedules you’ll know exactly what I mean when I say the schedule names can be really annoying.
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.
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.