stored procedure debugging in VS.NET

Correct me if I'm wrong, but I'm assuming if I leverage the built in stored
procedure debugging in VS.NET, that this potentially is locking resources on
our SQL Server. Moreover, this wouldn't be the best way of maintaining a
high performance database in general, and should be only used on a
development box. Correct?

Thanks in advance.

mark

re: stored procedure debugging in VS.NET

Correct - consider the case if you step debug over a "begin transaction" and
then {slowly at human speed} step debug to the "commit transaction"
statement; resources are locked while you are between the begin/commit
statements...

Yes you will want to debug on a development box..

"Mark" wrote:
[color=blue]
> Correct me if I'm wrong, but I'm assuming if I leverage the built in stored
> procedure debugging in VS.NET, that this potentially is locking resources on
> our SQL Server. Moreover, this wouldn't be the best way of maintaining a
> high performance database in general, and should be only used on a
> development box. Correct?
>
> Thanks in advance.
>
> mark
>
>
>[/color]

re: stored procedure debugging in VS.NET

Mark,

Yes. The debugging feature works great but you should only use this on a
development box not a production server.

Hope this helps.