I'm not 100% sure if this is the correct area to post this topic, but
I'll give it a shot.

I have just started working for a new company and came in a huge
scuffle between Network Admins and SQL Programmers. The problem is the
programmers want full administrator control on the sql server, but the
network admins refuse to give it to them stating they don't need it.
My question for the group is, what (if any) kind of access do SQL
programmers need on the SQL server?

Hi there,

This really depends on what the programmers will be doing. You should
ask your programmers what they want to do with the database and this
will guide what privileges they'll get.

If they will only be working with database objects such as stored
procs, views, tables etc then I would be tempted to only give them
db_owner privileges in the databases they will be working with.

I would find it unlikely that programmers would do sys admin tasks and
so there'd be little need to give them full rights. They only thing I
can think of is if they want to do performance monitoring they *might*
need higher privileges but if they don't mention it, then it probably
means they haven't thought about it.

This'll allow them to play with the database they are developing freely
but should still prevent them from doing naughty things in other
databases. If they require access to other databases (or specific
objects in other databases) then you can do this on an ad-hoc basis.

Hope that helps a bit, but sorry if it doesn't.

Normally they just need dbo rights on the database, if ysou want them
to create databases on their own you additionally have to place them in
the database creator role on server level. That should be enough if you
want to tighten up the security.

HTH, Jens Suessmeyer.

---
http://www.sqlserver2005.de
---