Re: Dbo role not the same on 2000 and 7

From: CD (mcdye1_at_hotmail.nospam.com)
Date: 09/17/04

  • Next message: Russell Fields: "Re: Dbo role not the same on 2000 and 7" 
    Date: Fri, 17 Sep 2004 15:06:55 -0500

    Thanks for the reply

    My test with trusted connection with those settings would not let them
    create a table from EM.

    "Russell Fields" <RussellFields@NoMailPlease.Com> wrote in message
    news:eYnxIbOnEHA.3712@TK2MSFTNGP15.phx.gbl...
    > CD,
    >
    > If you do not want them to be db_owner, then perhaps db_ddladmin,
    > db_datareader, db_datawriter.
    >
    > They will still be able to create objects owned by dbo, but must
    explicitly
    > say so in a create statement. E.g.
    >
    > NOT CREATE TABLE MyTable
    > BUT CREATE TABLE dbo.MyTable
    >
    > Russell Fields
    >
    > "CD" <mcdye1@hotmail.nospam.com> wrote in message
    > news:eZ2awbCnEHA.2948@TK2MSFTNGP11.phx.gbl...
    > > I was taken by surprise on this one. One of our transaction logs jump
    by
    > > leaps and bounds without our knowledge. Come to find out a developer
    had
    > > change the db properties on the transaction log to let it grow and then
    > > changed it back after he was done. On SQL7 a member of the db role
    could
    > > not make that kind of change. So now I am faced with needed help to
    best
    > > handle their new found ability.
    > >
    > > The development uses trusted connections and are a member of the
    db_role.
    > I
    > > have tired different combinations and different role but have not found
    > the
    > > perfect combination. I want to let them continue as they are accustomed
    > to
    > > BUT not change any DB properties (trans, data files sizes, options,
    etc.)
    > >
    > > Win03std, SQL2000sp3a+.876
    > >
    > > TIA
    > > CD
    > >
    > >
    >
    >

  • Next message: Russell Fields: "Re: Dbo role not the same on 2000 and 7"