|
|
Posted by serge on 01/26/06 15:49
> Personally, I have more or less stopped using the debugger. It usually
> works when you want to debug your local server, but when connecting to
> another, there is so much red tape.
Sometimes I do debug remotely (maybe often). Are you saying it is not always
a
safe approach to debug remotely? "There is so much red tape": these
are known issues that happen frequently or in the very rare cases?
Would you know if there are MS KB on these problems or personal
experiences led you to stop debugging remotely?
Can you please list some situations where debugging remotely is not safe
or the problems you ran into are complicated to explain?
If this is the case then I should avoid debugging remotely and end up
using Terminal Services to connect to the SQL Server and debug locally?
> Debug PRINTs and SELECTs are easier to handle.
I just tried "SELECT * FROM INSERTED" and I saw the result
in the results pane so I am not sure why I had not tried this before.
Well, at least now I know and I won't need to create a table if I am
only interested in seeing the result during the debugging only.
Thanks Erland.
Navigation:
[Reply to this message]
|