Event Notifications for Deadlock Graphs

Question

So, I was trying to setup emailing of deadlock graphs using event notifications. I followed the information I found in Jonathon Kehayias PASS information, but it appears (and maybe I am wrong) that event notifications and queues only work on
the database you create them under??? I see it says in BOL: http://msdn.microsoft.com/en-us/library/ms189453.aspx that it applies to the instance, but when I manually create a deadlock,
the queue only gets an entry if the deadlock was created accessing an object in the database where the queue was created. If I switch to another database, it does not add to the queue at all. Is that right? Or did I possibly configure something wrong? I can't
believe that events would be restricted to only fire in the database scope of the queue. That just sounds like it would essentially make this tool kind of useless for broader scoping work, like, anything actually instance related. Does anyone know? 
John M. Couch

Answer 1

Wow, I have a bunch of other stuff in there that maybe I don't need. I actually created a separate database. I am guessing that because you used MSDB that you did not have to enable the service broker using the code below:
-- Enable Service Broker
alter database [SysAdm]
set enable_broker;
go
I also noticed you did not create a route ? 
create route [CaptureDeadlockRoute] with service_name = 'CaptureDeadlockService', address = 'LOCAL';
go
And this appears to be where I screwed up. I did not pull the GUID and use it in the Event Notification creation, I simply used Current Database. 
-- Now query the sys.databases for the service_broker_guid of the msdb database.
SELECT service_broker_guid FROM sys.databases WHERE name = 'msdb';
In MSDB, create event notification using the GUID from above:
CREATE EVENT NOTIFICATION evnDeadLock_Graph
ON SERVER
WITH FAN_IN
FOR DEADLOCK_GRAPH
TO SERVICE 'svcDeadLock_Graph'
, '8D785814-2D75-490C-B07D-7303363A9B6B'; -- the GUID for msdb goes here
And I noticed you did not use the mail cert as in his code. Did it not work, or did you just skip it?
-- Create a certificate to sign stored procedures with
create certificate [dbaMailCert] encryption by password = 'dhsfosjf' with subject = 'Certificate for Sending Email via Stored Procedure';
go
-- Backup certificate so it can be create in master database
backup certificate [dbaMailCert] to file = 'R:\Path\dbaMailCert.CER';
go
-- Add Certificate to Master Database
use [master]
go
create certificate [dbaMailCert] from file = 'R:\Path\dbaMailCert.CER';
go
-- Create a login from the certificate
create login [dbaMailLogin] from certificate [dbaMailCert];
go
-- The Login must have Authenticate Sever to access server scoped system tables
-- per http://msdn.microsoft.com/en-us/library/ms190785.aspx
grant authenticate server to [dbaMailLogin]
go
-- Create a MSDB User for the Login
use [msdb]
go
create user [dbaMailLogin] from login [dbaMailLogin]
go
-- Add msdb login/user to the DatabaseMailUserRole
exec msdb.dbo.sp_addrolemember @rolename = 'DatabaseMailUserRole', @membername = 'dbaMailLogin';
go
John M. Couch