Divide and Conquer

Question

Divide and Conquer

Phil Factor

SSC-Insane

Points: 20244
More actions
March 22, 2014 at 3:26 am

#283746

Comments posted to this topic are about the item Divide and Conquer
Best wishes,
Phil Factor

Viewing 7 posts - 1 through 6 (of 6 total)

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

Yet Another DBA SSCarpal Tunnel Points: 4299 More actions · Answer 1

Been suggesting the use of schemas to developers since 2000 at different companies. But still too many of them want the quickest solution now and tomorrow is some distant event for someone else to sort out.

For me its been a useful technique, especially on the evolving projects.

Megistal SSCrazy Eights Points: 8787 More actions · Answer 2

Here, the schema is used as a namespace, a name container just like in .Net for instance, no security are used against them (anyway everything use SysAdmin role privilege, and no way they will changed that either).

Why? Simply because that "mentality" is closer to their working mind set (no one here understand / knows what the schema can be used for)

LightVader Hall of Fame Points: 3810 More actions · Answer 3

Megistal (3/24/2014)
Here, the schema is used as a namespace, a name container just like in .Net for instance, no security are used against them

I'm using schemas this way in the current project I'm developing. Though 2 of the schemas I intend to add security functions to as well.

The opinions expressed herein are strictly personal and do not necessarily reflect the views or policies of my employer.

mosaic-287947 Ten Centuries Points: 1053 More actions · Answer 4

It seems to me that schemas need to be part of the initial database design and will be used mainly for larger databases that need a formal design phase.

Many departmental databases started life as someone's informal personal project and are unlikely to have well thought-out schemas. And once they are in general use it is almost impossible to retro-fit schemas without breaking the automation and reporting scripts that will have sprung up around it.

Yet Another DBA SSCarpal Tunnel Points: 4299 More actions · Answer 5

mosaic-287947 (3/25/2014)
It seems to me that schemas need to be part of the initial database design and will be used mainly for larger databases that need a formal design phase.

It certainly helps to have a design phase.

Many departmental databases started life as someone's informal personal project and are unlikely to have well thought-out schemas. And once they are in general use it is almost impossible to retro-fit schemas without breaking the automation and reporting scripts that will have sprung up around it.

Yes it can be difficult, but also well worth while to implement. Leave it too late and it can be even more problematic.

Jon Russell Hall of Fame Points: 3048 More actions · Answer 6

Great article. I have been pushing the use of AD groups and schemas for years for adminstration purposes. Unfortunately, many do not want to take the time to set it up correctly. Now I will just send this article to explain the benefits of using a schema-based security model.