Developers' access to dev SQL Server

  • We have three environments in SQL 2005.. DEV, UA and Production. Developers do not have access to UA or Production (except for read-only some times).

    But how does your shop handle the development box? We currently create the db and make the developer dbo on that db but they are wanting full access to the entire instance. Do you do this? :unsure:

    Thanks,

    Bob

  • In our development environment, we give dbo access to the databases that the developer is working with, but not server(instance)-wide access.


    Thanks,

    Lori

  • I hesitate to give developers even DBO access for a simple reason. They don't necessarily keep track of things and they tend to make changes, try things, etc. without documenting them. Sorting things out later can be a hassle.

    Instead in 2005 I'd recommend you give them their own schema. They can test under their schema, create objects, etc. When they think things are ready to go, then promote their objects to the main schema (dbo or otherwise), search and replace any embedded schema in their code and you're ready to go.

    Or you can let them have developer edition on their workstation, create their own stuff and migrate it to the main branch, or main dev server, as it's ready for a larger scale test.

  • At my previous company, we gave the devs dbo access to the DBs that they were working on (on the dev server), however there was a DDL trigger in place that prevented any ALTER DATABASE statements unless executed by a member of the sysadmin group.

    That was done after one bright spark dev grew the data file on his database, set it to full recovery mode and 'forgot' to tell anyone. He started testing a large data load and went home. Backups ran at 6pm, log started growing immediately thereafter, dev box was out of space (completely) the next morning.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Who handles creation of Integration Packages, Replication Packages, creation of Analysis Cubes in your company if the developers do not have access to the SQL Server in Developement environment?

    Are all of you software developers too or just think application developers are not capable of working with SQL Server?

  • Not saying application developers don't know how to work with SQL Server, they just don't always think about things the same way a DBA.

    A DBA has a duty to protect the system, and that means providing application developers with only the access they require to do thier job, and nothing more.

    😎

  • Rian et all - I don't believe anyone is saything that developers can't or shouldn't have permissions in development but that the permissions should be limited to a NEED basis. There is a balance in trying to keep the environment safe, for all developers, as well as allowing the developer do their job, develop. Typically providing dbo permissions at the database level is sufficient for anything that can be done outside the scope of having a DBA involved. As Gail stated even putting some safeguards in place with that is wise so that other developers are not impacted by someone's carelessness or exploring. That wouldn't be responsible.

    So, that is the hurdle, selling the developers on the need to work with the limited permissions. That also puts the onus on us as DBA's to be responsive to their needs for changes that are outside of their permission / skill set.

    I'm all for having the developers having their own little dev environment on their machine that they can mess with to their hearts desire but when we start talking about a server that impacts others, sometimes in the 10's and 100's of others, there has to be some safeguards put in place.

    Make sense....

    David

    @SQLTentmaker

    β€œHe is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • I understand being a gate keeper is a tough job. But no one has still being able to answer my main question?

    Who handles the creation of Integration Packages, Replication Packages, creation of Analysis Cubes in your company if the developers do not have access to the SQL Server in Developement environment? Unless you are telling me that this can be done with dbo access.

  • Ditto to pretty much what every one else is saying. We have a dev box where the developers have access to the Db's and no one else's. Again for the same reasons, you don't want fun surprises to come into/get paged about because someone did something without thinking it through the whole way. I agree with DavidB 100%, that we need to be responsive as well...

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • Why not? I don't think any of those require sys admin access to the entire system to be completed. I can see where adjustments might be required, depending on what was being developed and how it is stored. For instance, SSIS packages being stored in SQL Server would require access to the msdb database.

    😎

  • So, you are telling me that I can create and administer Replication of databases (setup of publisher, distributor, creation of Merge Replication Rule and subscribers) without a sysadmin access to the SQL Server.

  • I guess I wouldn't see replication as a development role. There are far too many things associated with replication, i.e. the jobs, configuring of the agent and the agent profiles, the distributor, managing the distribution database, etc. that are DBA related and really require sysadmin permissions. If you are doing that then ask for a seat over with the DBA's. πŸ™‚

    David

    @SQLTentmaker

    β€œHe is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • I have to agree with DavidB, setting up replication is not a developer task. It should be setup by the DBA. Too many things that need to be taken care of to ensure it is properly set up.

    😎

  • So, one can setup replication (creation of Distributor, Publisher, Subscribers and creation of Merge Replication scripts) with dbo access.?

  • What Lynn and DaveB are saying is that they feel (and I agree) that it's the responsibility of the DBA to set up replication. While we've had developers set up OLAP processes and SSIS packages, I haven't run into developers that set up replication.


    Thanks,

    Lori

Viewing 15 posts - 1 through 15 (of 42 total)

You must be logged in to reply to this topic. Login to reply