Update README.md

BrentOzar · web-flow · commit 7c8c31c31000 · 2024-04-18T14:38:47.000-07:00
Clarify that sp_BlitzLock won't always work in Azure SQL DB.
diff --git a/README.md b/README.md
@@ -329,6 +329,7 @@ Parameters you can use:
 
 Known issues:
 
+* In Azure SQL DB, Microsoft doesn't seem to be running system health sessions for you. If you get the error "A session with the name system_health does not exist or is not currently active", you'll need to start your own Extended Events session to capture deadlocks. We don't have documentation on that, unfortunately, but we'd love to get help from someone else writing that!
 * If your database has periods in the name, the deadlock report itself doesn't report the database name correctly. [More info in closed issue 2452.](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/2452)
 
 

Original file line number	Diff line number	Diff line change
`@@ -329,6 +329,7 @@ Parameters you can use:`
`329`	`329`
`330`	`330`	`Known issues:`
`331`	`331`
	`332`	`+* In Azure SQL DB, Microsoft doesn't seem to be running system health sessions for you. If you get the error "A session with the name system_health does not exist or is not currently active", you'll need to start your own Extended Events session to capture deadlocks. We don't have documentation on that, unfortunately, but we'd love to get help from someone else writing that!`
`332`	`333`	`* If your database has periods in the name, the deadlock report itself doesn't report the database name correctly. [More info in closed issue 2452.](https://github.com/BrentOzarULTD/SQL-Server-First-Responder-Kit/issues/2452)`
`333`	`334`
`334`	`335`