Lesson Learned #209: Hands-On-Labs:10928-Resource ID:1.The request limit for the database is reached

[Jose_Manuel_Jurado]

We used to have cases where our customer faced the following error message: "10928-Resource ID : 1. The request limit for the database is x and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance." in this video below we are going to give some insights about it.

The Resource ID x indicates the resource that has reached the limit. You could find more information here 

• When Resource ID = 1, this indicates a worker limit has been reached. Learn more in Error 10928: Resource ID : 1. The request limit for the database is %d and has been reached. 
• When Resource ID = 2, this indicates the session limit has been reached.

In this video we will cover scenarios causing error - 10928-Resource ID:1.The request limit for the database is reached and mitigation steps.

Why this issue happens?

• Occurs when you reach the maximum number of requests (concurrent operations) available for your database (hard limit).

How to find the number of requests are running?

• SQL SERVER Management Studio

• Overview Blade in the portal

How to fix the issue?

• Stop the request/Close all connections.

• Review database performance.
  • Tune and optimize your queries as this will help with request limit issues in future. Review this article Lesson Learned #119: What is the query that my stored procedure is running now? - Microsoft Tech Com...
  • Review the indexes rebuild and update statistics using How to maintain Azure SQL Indexes and Statistics - Microsoft Tech Community
  • Treat the exception that your application gets whenever the limits of Logins are reached and retry the operation. 
  • You can apply recommendations from portal to improve query performance or review the missing indexes. Review this link to obtain all the best practices - Lesson Learned #195: Performance Best Practices for Azure SQL Database and Managed Instance. - Micro...
  • If you need to test your worload review this link: Lesson Learned #196: Latency and execution time in Azure SQL Database and Azure SQL Managed Instance...
• Scale up your database.

Enjoy!