Error/Fix: The Extended Events session named “blocked_process” could not be found.
Two days back while I am presenting in a KT session within team on how to use Extended Events for trapping blocking and deadlocks, and use the SQL Sentry Plan Explorer to analyze deadlock graph in detail. I was greeted with below error message when I tried to click ‘Watch Live Data’ for my extended event session.
Resolution: After spending few minutes on google, I found this link that resolved my issue. Basically my login had a different default database than the [master] database. When I changed my default database to [master], the error went away, and I was able to Watch Live Data on the extended event sessions.
One can use below code for changing the default database for login.
ALTER LOGIN <Login_Name> WITH DEFAULT_DATABASE=[master]
Once above changes were made, I was successfully able to Watch Live Data of Extended Event session. Happy Coding
Analyzing Deadlock Issues
2 Comments | Feb 21, 2017
About The Author
I am Microsoft Certified Professional having 10+ years of experience in SQL Server Querying, Database Design, and Administration. I am fond of Query Tuning and like to automate things using TSQL & PowerShell. I also have experience of implementing end-to-end Data Warehouse solution, and Data Migration using ETL tools SQL Server Integration Services (SSIS), Pentaho Business Analytics, and have designed Database Inventory through PowerShell, Python, and Django etc.