3

In our current environment, developers are not allowed to use SQL Debugging against any of the QA servers. It's not clear to me why the decision was made.

What factors should be considered to decide in favor or against enabling SQL debugging?

I'm looking at QA servers that are not used for production, but are shared among a dozen teams working on unrelated projects. Our developers cannot run local databases for a variety of reasons.

EDIT: To clarify, the servers are called QA, but they really are a mixed "development/preliminary QA" servers. There are separate UAT servers.

Euro Micelli
  • 133
  • 2
  • 5

3 Answers3

4

Yes. In order to use the T-SQL debugger, members must be members of the sysadmin fixed server role. That gives them complete rights over the SQL Server. That's not something you want to give out to developers in a QA or production environment. Development may be a different story.

Reference: SQL Server 2008 Books Online - Configuring and Starting the Transact-SQL Debugger

K. Brian Kelley
  • 9,034
  • 32
  • 33
1

Additionally, if you debug you can halt processes on the Sql Server, stopping anyone else from acting while you are actively debugging. If the server is shared by a large number of teams, that can be a problem.

Pete
  • 111
  • 1
  • 3
0

Enabling debugging will take additional resources on the machine, but otherwise I can see no reason to disable this. Perhaps there are security concerns with the data?

Chris Ballance
  • 304
  • 1
  • 7
  • 20