We used to have cases where our customer faced the following error message: "10928-Resource ID : 2. The session 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 : 2. The session limit for the database is x and has been reached and mitigation steps.
Why this issue happens?
- Occurs when you reach the maximum number of connections available for your database (hard limit).
How to find the number of session opened?
- SQL SERVER Management Studio
How to fix the issue?
- Close all connections.
- Scale up your database.
Enjoy!
Updated Jun 28, 2022
Version 4.0Jose_Manuel_Jurado
Microsoft
Joined November 29, 2018
Azure Database Support Blog
Follow this blog board to get notified when there's new activity