Database Administration
in [General]
|
From: "Bob McConnell" on 24 Sep 2010 15:50 From: tedd >At 2:36 PM -0400 9/24/10, Bastien Koert wrote: >>On Fri, Sep 24, 2010 at 2:26 PM, tedd <tedd.sperling(a)gmail.com> wrote: >>> At 2:09 PM -0400 9/24/10, Bastien Koert wrote: >>>> >>>> @tedd, >>>> >>>> He wants not techie users to create new systems for their clients when >>>> they sign up. It involves creating a DB and he's wondering about >>>> security for that. The main part of the app needs the least priv's to >>>> run (select, update, insert [,delete]) while the creating the DB >>>> obviously takes more. The OP was asking how to best handle that since >>>> the he didn't want to give the main app DB user account more privs >>>> than needed. >>> >>> Okay, what does creating "new systems for their clients" mean? >>> >>> What I want to know is specifically what these non-techie users intend to >>> do? >>> >>> Please don't answer that they want to set up accounts for their clients >>> because that is meaningless to me. That could mean anything. >>> >> > So, what specifically are these non-techie users going to do? >> >>Create a DB schema, create and populate tables. > > Creating a DB schema is not for non-techies -- you really need to > know what you are doing to do this. > > But we all live with what we create. I suspect he actually means create a new table using a predefined schema. But unfortunately, he doesn't appear to know enough about the problem to be able to explain it. He is either in way over his depth, or hasn't done a very good job of defining his requirements. Bob McConnell
From: Bastien Koert on 24 Sep 2010 15:58 On Fri, Sep 24, 2010 at 3:50 PM, Bob McConnell <rvm(a)cbord.com> wrote: > From: tedd > >>At 2:36 PM -0400 9/24/10, Bastien Koert wrote: >>>On Fri, Sep 24, 2010 at 2:26 PM, tedd <tedd.sperling(a)gmail.com> wrote: >>>> At 2:09 PM -0400 9/24/10, Bastien Koert wrote: >>>>> >>>>> @tedd, >>>>> >>>>> He wants not techie users to create new systems for their clients > when >>>>> they sign up. It involves creating a DB and he's wondering about >>>>> security for that. The main part of the app needs the least priv's > to >>>>> run (select, update, insert [,delete]) while the creating the DB >>>>> obviously takes more. The OP was asking how to best handle that > since >>>>> the he didn't want to give the main app DB user account more privs >>>>> than needed. >>>> >>>> Okay, what does creating "new systems for their clients" mean? >>>> >>>> What I want to know is specifically what these non-techie users > intend to >>>> do? >>>> >>>> Please don't answer that they want to set up accounts for their > clients >>>> because that is meaningless to me. That could mean anything. >>>> >>> > So, what specifically are these non-techie users going to do? >>> >>>Create a DB schema, create and populate tables. >> >> Creating a DB schema is not for non-techies -- you really need to >> know what you are doing to do this. >> >> But we all live with what we create. > > I suspect he actually means create a new table using a predefined > schema. But unfortunately, he doesn't appear to know enough about the > problem to be able to explain it. He is either in way over his depth, or > hasn't done a very good job of defining his requirements. > > Bob McConnell > The OP mentioned that each new client needed their own DB so that is how I took it. Having exactly the exact same tables in the structure with different names is just bad practice to. That just screams creating a multi-tenant DB. At work we do create each DB as a clone of a master table, but it is done manually and thankfully not that often. -- Bastien Cat, the other other white meat
From: Tom Barrett on 30 Sep 2010 11:57
Thanks for the replies, they have been most enlightening. :) |