A group in our organization (DAG- Data Architecture Group) are pushing to add some tables and procs to the master database. The DBA's, including me, don't like the idea of non-system object in the master database. Does placing non-system object in the master database go against any best practices that you can think of? Any problems in upgrading? Is there supporting docuementation out there?
This group (DAG) have created these tables to monitor there own customized replication process as well as storing audit information about database changes. Both are home grown solution that I have my reseveration about.