Divide and Conquer

  • Comments posted to this topic are about the item Divide and Conquer

    Best wishes,
    Phil Factor

  • 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.

  • 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)

  • 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.

  • 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.

  • 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.

  • 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.

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

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