MS DB Development Scenario

[JBB]

Let me preface this question by saying that I've worked in a variety of development environments/scenarios, with various numbers/sizes of teams/groups, and varying management styles.  This question regards the style used to manage a development group's (multiple teams on separate projects) use of a single MS SQL Server database that is used by all teams in the group to develop stored procedures, etc.

I'm also obviously biased in favor of the Developers having more control than what I'm about to describe.  I'm interested in knowing what you think and whether or not you think the level of control granted to the developers is too restrictive or not restrictive enough or just right.

1.  Non-developer DBAs manage the database server and configure all rights, permissions, backups, and restores.

2.  Developers are not allowed to use the following
     A)  Kill - can not kill any process
     B)  SQL Profiler - can not run/use SQL Profiler
     C)  Can not access any system tables in the Master
          database
     D)  Can not schedule jobs in SQL Agent
     E)  Can not add new DTS packages or delete old
     F)  Can only use SQL Debugger if a DBA grants permission

So what do you think?  Is this level of control / style of management appropriate?

[emg2]

I've never had the privileges listed except on the instance of SQL Server running on my home machine.  It just goes with the territory of multiple developers sharing a common resource.

[KRG316]

I've been mostly on the opposite end of the spectrum - developers have full access/privileges to the development database.  Obviously you need to have developers who won't go dropping things all over the place to make this work.  Everywhere I've worked where we've had these privileges it's worked out fine, though.

[Jeremy Singer]

If the developers can do the things you said, it should only be for the development database.

Usually, I have worked in places with staged development, where there is a Development/QA/UAT/Production set of databases.

As I said, all but the development database should be off limits to developers.

That said, I have had the role of DBA and developer.  You need to be very careful that you don't mess up the other developers when things are set up this way.