Re: Developers Access in PROD

From: BP Margolin (bpmargo@attglobal.net)
Date: 05/31/02 

From: "BP Margolin" <bpmargo@attglobal.net>
Date: Fri, 31 May 2002 17:01:05 -0400

Dinky,

I was assuming that you were talking about developers on a development box.
Sorry if I misunderstood you.

If you are talking about developers accessing a production box, then that is
a much more complicated matter.

The first concern is the sensitivity of the production data. If the data is
sensitive, then I have seen shops where developers are not permitted any
access to the production box. This obviously implies that any bugs that are
encountered in the production system must be re-created on the development
or staging box so that the developers can see exactly what the problem is.

If the data is not sensitive, then normally developers might be restricted
to a read only mode.

In either case, I am assuming that there is a mechanism in place so that
developers can make changes to the development or staging box, and for such
changes to be migrated to production.

-------------------------------------------
BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
can be cut and pasted into Query Analyzer is appreciated.

"Dinky" <dinh.nguyen@dewr.gov.au> wrote in message
news:8d9901c20856$128e23b0$36ef2ecf@tkmsftngxa12...
> BP Margolin,
>
> To me the developer should have different kind of access
> with users in PROD. If we give db_owner access to users,
> also as developers, so both of them can create or drop an
> object (table, SP etc...) in PROD, that it should not be
> allowed in PROD, I think.
>
> What I am thinking to do is somehow I want to give
> developers browsing database structures only in PROD,
> that I can prevent developers to "select" or DTS data to
> another server. I wonder that there is any way we could
> we do it in SQL Server that I know that we can do it in
> another DBMSs.
>
> D
> >-----Original Message-----
> >D,
> >
> >Typically, I'm willing to give application developers
> db_owner permissions.
> >
> >One just needs to make sure that when testing an
> application, that the
> >developers log in to the database with a login that is
> set to the
> >permissions that one expects the login to have in
> production.
> >
> >-------------------------------------------
> >BP Margolin
> >Please reply only to the newsgroups.
> >When posting, inclusion of SQL (CREATE TABLE ...,
> INSERT ..., etc.) which
> >can be cut and pasted into Query Analyzer is appreciated.
> >
> >"Dinky" <dinh.nguyen@dewr.gov.au> wrote in message
> >news:9b3401c20843$1f47deb0$b1e62ecf@tkmsftngxa04...
> >> Folks,
> >>
> >> In your SQL Server shop, what kind of access has been
> >> given to application developers? ie. db_reader,
> >> db_owner, public etc...
> >>
> >> Thanks
> >>
> >> D
> >
> >
> >.
> >

Relevant Pages

  • RE: MS SQL Farm
    ... Regards ... > infrastructure that will help us leverage MS Sql server. ... > implementation and design will be done by us developers. ... > development/test and production servers with stand by servers. ...
    (microsoft.public.sqlserver.clustering)
  • Re: various comments (a.k.a. dull monologue coming up)
    ... Vectrex universe. ... I think that you and other developers out there will always find the users ... overlay and gameplay (and box production) (as a matter of fact i also ... vector/50% raster based. ...
    (rec.games.vectrex)
  • Re: Proof of concept - Segregation of developers
    ... Vlan are best, but need to be done by Mac address. ... Proof of concept - Segregation of developers ... if there exists the need to physically separate these guys vlan of development/test and production environment? ... Cenzic Hailstorm finds vulnerabilities fast. ...
    (Pen-Test)
  • Re: why administrator refuse to give permission on PLUSTRACE
    ... have access to a production database except as an end-user utilizing the ... only happen where the developers know what they are doing, ... I currently support - it isn't typically a mini-app. ... then the DBA won't be the guy who knows the business rules implemented by this ...
    (comp.databases.oracle.server)
  • Re: Why do IT guys hate MS Access?
    ... been involved in situations where an Access production application, ... by profesional developers, was successfully managed and operated by users, ... is Access used as "a prototyping tool". ... seen some applications start out as "prototypes" but become "production ...
    (comp.databases.ms-access)