[Video] Top 3 Pitfalls of Managing Your Azure SQL DB Costs
You manage servers, not invoices. Your company has started to move their databases into Azure, and they’re asking questions that you’re just not ready to answer. How big does your server need to be when you’re moving an existing database up to the cloud? How are servers measured? How do you measure to know if your new Azure SQL DB is overwhelmed, or if it’s a code or index problem? How do you make the right adjustments once you’re up there?
In some webcasts, I give you all the answers. In this webcast, I’m mostly just giving you the questions – but I’d rather have you learn them quickly in a short webcast instead of learning ’em the hard way. Here goes:
If you enjoyed this webcast, you can catch me doing ’em live by following me on Twitch, YouTube, or Facebook.
Related

Hi! I’m Brent Ozar.
I make Microsoft SQL Server go faster. I love teaching, travel, cars, and laughing. I’m based out of Las Vegas. He/him. I teach SQL Server training classes, or if you haven’t got time for the pain, I’m available for consulting too.
Get Free SQL Stuff
"*" indicates required fields

3 Comments. Leave new
Excellent Brent! like always.
Valid too for AWS RDS SQL SERVER 😉
Best!
lol you don’t manage invoices until you move to the cloud and then suddenly its the only thing you do and you also have 3 more dbas you didn’t have before tunning queries
before, tuning queries.*