Commit 07303a5
Distinguish missing vs inactive session in Azure system_health check
Address review feedback: only show the friendly "not available" message
when the system_health session truly doesn't exist in
sys.database_event_sessions. If someone creates a database-scoped
session named system_health but forgets to START it, they now get the
original severity-11 "does not exist or is not currently active" error.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>1 parent e2d85ed commit 07303a5
1 file changed
Lines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
571 | 571 | | |
572 | 572 | | |
573 | 573 | | |
| 574 | + | |
| 575 | + | |
| 576 | + | |
| 577 | + | |
| 578 | + | |
| 579 | + | |
| 580 | + | |
574 | 581 | | |
575 | 582 | | |
576 | 583 | | |
| |||
0 commit comments