Sql Server Debugging Rights For Standard Developers
Solution 1:
You must have syadmin rights in order to be able to debug SQL (see How to: Set SQL Server Permissions for Debugging)
Debugging SQL isn't something that should be done on production machines - in the words of Microsoft:
Debugging sessions often run for long periods of time while you investigate the operations of several Transact-SQL statements. Locks, such as update locks, that are acquired by the session might be held for extended periods, until the session has ended or the transaction is committed or rolled back.
Definitely not a good idea for production machines.
(I'm assuming that this was for a production SQL server - restricting permissions for devs on non production servers seems kinda pointless)
If you need to debug against on a production machine because of the live data then just do the debugging on a mirror / backup of the live data.
Solution 2:
You only need execution rights (as far as I know) - I'm certainly no sysadmin but I can debug SQL
Post a Comment for "Sql Server Debugging Rights For Standard Developers"