Hi

Actually, Im really against this sort of security mentioned by Chris L for
dev machines. The developers should not have SA access (on their local PC
is fine), perhaps ddladmin and security admin for selected databases they
are working on, but that's it. Its very important as a DBA to have
managenle control over your database, its schema, security privs/roles
allocated, and manage as developers request access to xp_cmdshell (for
example) and perform other magical tasks to complete their app. As a DBA
you don't want to be dealing with a host of issues related to slack work on
the dev boxes that make their way into prod.

Off track of the profiler q of course :)

Cheers

Ck

MS Sql Server LazyDBA home page