Azure Purview is a compliance and data governance platform in Microsoft’s Azure cloud. The platform is currently in public preview and has quite a few features; but, does not currently import any of the extended properties that you may have added over the years to your SQL Server objects.
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.
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.
Simple post today: How to compare two plans in SSMS.
This task is a task that is often done by a DBA or developer who is wanting to compare changes of an index or perhaps even comparing queries between DEV and PROD.
Microsoft recently introduced a handy new feature to query plans: waitstats. That’s right, you can get actual runtime waitstats for a query you run.
It seems like SSMS has seen better days. Many developers I have worked with recently complain about Out of Memory issues and other bugs and I personally miss the days of Query Analyzer.
If you’ve read my blog, I’m sure by now you know that I have no love for GUI tools. I will say they are improving every day and maybe, just maybe, we will see the day when you can click happily away and do everything you want. Sadly, this is not the day.
A while back, SSMS added the “Missing Index” data to the graphical query plan. They even made it really easy to add.
People always ask me what tools I use. Mostly this question comes from the topic of monitoring. I can honestly say that I don’t love any tools and you shouldn’t either.
My time at Microsoft placed me at nearly 300 different clients. As a Microsoft employee I never liked saying, “Go grab this tool so we can look at your problem because SSMS isn’t good enough.”
I’ve been testing the new Temporal Tables feature over the past day to see about using it in one of our production databases. It’s a neat feature that honestly adds a boat load of possibility around logging.
In my testing I noticed that user created tables seem to store the rows over quite a bit more pages. User created history tables were nearly double the size of an auto generated one. If you’re currently using the feature or plan to use it in the near future, you’ll want to think about this storage issue before you implement.
If you have just begun using SQL Server 2016 or you have been using it for a while now you may not have noticed the new MAXDOP settings.