If the database is MS-SQL and you want to organize your objects to reduce the risk of editing the wrong object, then I don't recommend you to create a separated DB. MS-SQL provides the schema functionality. Just create a new schema, and put all objects there. Then create a user with privileges only at this schema. Thus, this user will only see the external objects and wont see the Remedy ones. Give this user to people that must edit those objects. Remedy will be able to see those objects because they are at the same database. Also the impact on the database is null, since they are at the same database.
Jose Manuel Huerta http://theremedyforit.com/ On Fri, Sep 7, 2012 at 9:08 PM, Jason Miller <jason.mil...@gmail.com> wrote: > MS SQL 2008 Standard 64-bit _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
