Found out that all our Azure SQL Databases (pricing tiers S1-S2) have high number of connections/sessions from SA

SA - BRKR TASK - around 60 sessions
SA - TASK MANAGER - around 20 sessions

Here are two questions:

1. What are those ? 
2. Why so many connections from them on Azure SQL databases ?

The reason I ask is sometimes it causes error

"The request limit for the database is (paste a number here) and has been reached"



Those BKRK are related system processes and back end connections and do not count upon the limit of connections associated with every service tier. They can safely be ignored. BKRK processes are related to service broker on on-premises SQL Server instances and Azure SQL Database may be using it as part of the service it provides.

With Azure SQL Database you will always see many connections and processes related to the automated features the PaaS provides to the customer. Learn more about back end connections here.

Instead of focus on system processes, please try to know if blocking is the culprit.

select r.session_id,r.blocking_session_id,r.wait_type,r.wait_time,r.wait_resource,r.total_elapsed_time,r.cpu_time,r.reads,r.writes,
from sys.dm_exec_requests r
join sys.dm_exec_sessions s
on s.session_id=r.session_id

Consider also deadlocks may be a possibility, and you can find them using below query.

select *
from sys.event_log
where event_type <> 'connection_successful' 
and start_time >= CAST(FLOOR(CAST(getdate() AS float)) AS DATETIME)
order by start_time desc  -- event type = deadlock
|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.