Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
denis_the_thief
Aged Yak Warrior
596 Posts |
 Posted - 2010-10-22 : 10:30:00
|
| According to BOL, Developers must belong to sysadmin in order to debug. We would like to avoid that - does anyone know of a work around?And I find it hard to believe SQL Server has that behavior - it's like saying only DBAs can debug - or Developers should be entitled to full priviledges. |
|
|
Sachin.Nand
2937 Posts |
Posted - 2010-10-22 : 14:06:32
|
| Why should a developer be allowed to do something which is none of his concern?PBUH |
 |
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2010-10-22 : 14:38:48
|
quote:
Originally posted by Sachin.Nand
Why should a developer be allowed to do something which is none of his concern?PBUH
It's his concern because he wrote the darn thing! I guess you only allow 'DBAs' to write your Stored Procedures but it is pretty common to have Web Developers, Application Developers and/or Database Developers to write them too. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-10-23 : 02:21:22
|
| why not add a role for developers and give them only required access like DENY execute rights on sensitive sps, permissions to sensitive tables etc------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2010-10-24 : 01:42:29
|
do you want to allow your devs to debug against prod machines? bad idea if it means giving them sysadmin access to prod.normally one would have a dev/test environment where devs can set up access as needed for debugging.
elsasoft.org |
|
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2010-10-25 : 08:42:32
|
quote:
Originally posted by jezemine
do you want to allow your devs to debug against prod machines? bad idea if it means giving them sysadmin access to prod.normally one would have a dev/test environment where devs can set up access as needed for debugging.
elsasoft.org
Good points. That's the thing, we want them to debug but don't want them to have have sysadmin. Actually this is not for Prod, we have QA and Dev Databases on the same server. We don't want them to have sysadmin on this server - one reason is so that they can't modify table structure on QA Databases, it has to go through Dev Databases first and tracked. |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2010-10-25 : 12:11:19
|
if you really have to have dev and qa share the same server, you could use named instances of SQL Server. that way you could give dev whatever rights they need to debug, and still have them locked out of the QA instance.
elsasoft.org |
|
|
|
|
|
|
SQL Server Debugging for Developers