RE: [SQLDownUnder] Master database & oops part 2

[Wheat, Mitch]

Greg

 

I totally agree. How often does anyone make changes to the master database? I try to avoid it.

It's funny but after reading your post yesterday, I thought about it later and came to the same conclusion, you shouldn't really be able to modify the master database accidently. Changes to it should require something like an explicit command.

 

Mitch

-----Original Message-----
From: Greg Low [mailto:Greg.Low@xxxxxxxxxxx]
Sent: Thursday, 3 March 2005 5:38 PM
To: sqldownunder@xxxxxxxxxxxxxxxxxxxxxx
Subject: [SQLDownUnder] Master database & oops part 2

I was in an Ascend class with Bob Beachemin yesterday and saw yet another
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

to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net

EOM

---

EMAIL DISCLAIMER NOTICE

This message is the property of HATCH.  The information in this email is confidential and may be legally privileged. It is intended solely for the addressee.  Access to this email by anyone else is unauthorised.  If you are not the intended recipient, any disclosure, copying,distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

If you have received this message in error please notify HATCH immediately via e-mail to : mailadmin@xxxxxxxxxxxx

For more details about HATCH visit http://www.hatch.com.au

---