| [SQLDownUnder] Master database & oops part 2 |
- From: Greg Low
- Subject: [SQLDownUnder] Master database & oops part 2
- Date: Thu, 03 Mar 2005 20:23:38 +1100
- Follow-Ups:
- Re: [SQLDownUnder] Master database & oops part 2, Darius Zakrzewski
- Prev by Date: Re: [SQLDownUnder] Adelaide SIG meetings?
- Next by Date: RE: [SQLDownUnder] Master database & oops part 2
- Previous by thread: RE: [SQLDownUnder] Master Database & Oops
- Next by thread: Re: [SQLDownUnder] Master database & oops part 2
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
person run a script in the master database when they meant to be elsewhere.
I realised you could now basically fix that with a DDL trigger in SQL Server
2005 (blogged about it at http://msmvps.com/greglow).
However, it struck me that I'd really like a server option that says
"Protect master schema" or something (as an advanced option), rather than
having to even set up a trigger. I mentioned it to one of the dev guys and
he seemed lukewarm yet every single person I've mentioned it to so far says
"oh yes yes please". I got Dave Lean to post a request on it last night but
I wanted to get your opinions.
Would that be useful? Can you see any problems?
I'm just figuring that 99.9% of DDL mods to master are in error and should
be prevented by default.
Thanks,
Greg
(Click here for more information on the sqldownunder mailling list)
