July 16, 2008 at 6:50 pm
I need to separate the stored procs used for reporting from the stored procs used by the application (mission critical).
I have not used schemas before so am unaware of any defining factors which would tip the balance one way or another.
Each developer has a separate db which they development on. The changes are then scripted up and imported into the live db. Does this process affect schemas?
any advice is appreciated
July 16, 2008 at 8:40 pm
Schemas are a way to separate out objects and assign permissions. You could have all stuff moved into one of two schemas, which would make production administration easier.
You still have to manage merging from the various developers, but if you have them create things in the schema in their database, it makes things easier.
July 16, 2008 at 9:35 pm
Thanks Steve, its appreciated.
July 17, 2008 at 12:08 am
Its true Schemas differentiates the objects it wont affect your process unless you make changes in your application for stored procedure belongs to schema. E.g. If you are specfiying usp... then if you define it under schema rpt then you hvae to specify as rpt.usp....
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply