If you’ve ever been a DBA and seen the mess that you get with SQL Agent Jobs without a clean naming standard for your job schedules and job names then you’ll appreciate this tip.
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.
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.
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?
If you’re a data professional or application developer chances are you’ve run into Microsoft SQL Server once or twice.
It’s taken longer than I thought it may and I’ve run into several problems along the way but had a few people in the MVP community swing some homeruns to help me complete the BETA of this new SQL Server community query tuning tool.