Recommendations on creating user-objects on system database I want to setup a bunch of Event Notifications on SQL Server using Service Broker for our production database.

I've setup a new database on my testing machine, and everything works well.
The problem is that I'd rather not have to deploy a whole database for this notification purposes and I can't use one of the user databases already in place (that would be a mess, anyway).

If possible, I'd preferably deploy the notification objects on master, but first I'd like to be sure this is actually a good idea (if it actually is).

From Books Online:


  Do not create user objects in master. If you do, master must be backed up more frequently.


Books Online recommends I do not create user objects in master, but in this case, I don't think it's that much of a problem since I don't really care if I eventually lose some notification data. Besides, we already do backup our master database frequently.

Should I use the master database or something else in this case?

Is there something I should know about the master database, Service Broker or Event Notifications before setting this up?
I can think of a few questions about this implementation that I would want to know before continuing:


What happens if, somehow, microsoft creates an object with the exact same name in a new version?
If databases are migrated to a new server, how will anyone know that there's something in master to migrate?
What happens if your objects corrupt the master database?
What adverse affects would having extra data in master have on the instance?
What would happen if an in-place upgrade was performed on this instance? (ie, upgrading 2008 to 2008 R2)
How would restoring the entire instance from backups be affected?


Most of these I don't know the answer to, but they're questions that come up when I contemplate putting objects in master.