This is a good article!

Question: the stored procedure LogginProc is doing the endless loop waiting for the logon event description to be queued and when it finds one it pulls the information from the queue. Is it really a trigger? I can do the similar thing with the traces. You just set up a server-side trace with logging to the trace file. Than the logon events will be logged to the trace file. Then you can select from the trace file into any table or you may select to keep this info in the trace file because you can query it too by fn_trace_gettable. I do understand that we will have to wait until trace file rolls over to get the information but it will be logged anyway.

But in general, this article is a very good and easy to understand example on how to use the Service Broker.

...
2009-02-27 17:07:35.01 spid14s     Error: 9644, Severity: 16, State: 14.
2009-02-27 17:07:35.01 spid14s     An error occurred in the service broker message dispatcher, Error: 15517 State: 1.

ALTER AUTHORIZATION ON DATABASE::[My_DB_Name] TO [SA];