user objects in master

  • paul Arscott

    Mr or Mrs. 500

    Points: 504

    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.

  • Grant Fritchey

    SSC Guru

    Points: 396617

    Books online recommends not placing objects in Master. I'd recommend against it too.

    Truth is, you can put objects there. You'll have to be much more careful about backups. You might expose security holes in your system, so be very restrictive in access to master. Always remember, if master goes away, so does the server.

    The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
    Theodore Roosevelt

    The Scary DBA
    Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd Edition
    Product Evangelist for Red Gate Software

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply