未加星标

Azure SQL DB is Slow: Do I Need to Buy More DTUs?

字体大小 | |
[系统(windows) 所属分类 系统(windows) | 发布者 店小二04 | 时间 2018 | 作者 红领巾 ] 0人收藏点击收藏

You’ve got an Azure SQL DB, and your queries are going slow. You’re wondering, “Am I hitting the performance limits? Is Microsoft throttling my queries?”

There’s an easy way to check:run sp_BlitzFirst. sp_BlitzFirst is our free performance health check stored procedure that analyzes a lot of common performance issues and then gives you a prioritized list of reasons why your server might be slow right now.

Here’s what it looks like when you’ve hit your DTU limits note that there are multiple rows, one for each 15-second period where you approached or hit your DTU limits in the last 15 minutes:


Azure SQL DB is Slow: Do I Need to Buy More DTUs?

Azure SQL DB is maxing out

If you click on the “ClickToSeeDetails” column, you get:

<?ClickToSeeDetails -- At 2018-10-21 17:02:09.153, your database approached (or hit) your DTU limits: Average CPU percent: 99.88 Average data IO percent: 0.00 Average log write percent: 0.32 Max worker percent: 2.22 Max session percent: 0.88 -- ?>

We’re checking the last 15 minutes of the sys.dm_db_resource_stats management view to see if you hit 90% or higher for avg_cpu_percent, avg_data_io_percent, avg_log_write_percent, avg_memory_usage_percent, max_worker_percent, or max_session_percent.

Uh oh I’m maxed out. Now what?

You could tune queries, tune indexes, lower your app’s workload, or upgrade to a higher DTU limit.

To find which queries to tune, runsp_BlitzCache @SortOrder = ‘___’, where ___ is based on which limit you’re hitting:

CPU limits run sp_BlitzCache @SortOrder = ‘cpu’ Data IO run sp_BlitzCache @SortOrder ‘reads’ Log write run sp_BlitzCache @SortOrder = ‘writes’

If you’d rather tune indexes, runsp_BlitzIndex and focus on the missing index warnings. They’re chock full of dangerous pitfalls, but they’re still one of the easiest ways to get started. We teach you how to interpret the recommendations in our Fundamentals of Index Tuning videos.

Lowering your app’s workload is a totally valid option, too: try caching things in your application rather than hitting the database every time, or staggering your workload so that queries are run at different times.

And of course, you could throw hardware at it by raising your DTU level. If you started on a really low level, like S1/S2/S3, and you’re constantly hitting these throttling limits, then it might be time to upgrade. To keep things in perspective, an S4 with 200 DTUs is only $300/month if you’re any lower than that, you’re probably going to hit limits sooner rather than later.

All these scripts are part of our free First Responder Kit .

本文系统(windows)相关术语:三级网络技术 计算机三级网络技术 网络技术基础 计算机网络技术

代码区博客精选文章
分页:12
转载请注明
本文标题:Azure SQL DB is Slow: Do I Need to Buy More DTUs?
本站链接:https://www.codesec.net/view/621312.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(windows) | 评论(0) | 阅读(42)