February 24, 2005 at 9:22 pm
In our stored procedures we have many print statements that we utilize for debugging, is there a switch that can be set on the 1st stored procedure that is called (we are nesting them) where it can turn off the print statements - so that it does not communicate with the desktop until all stored procedures close?
February 24, 2005 at 10:21 pm
So you have debugging code in your production stored procedures ?
Well that's another issue ...
How about the tried and tested method of passing through a flag that indicates if you're debugging or not?
Then in your stored procedure you have,
IF @isDebug = 1 PRINT 'This is a debug message... remainder of code ...
--------------------
Colt 45 - the original point and click interface
February 24, 2005 at 11:57 pm
Yes that would work under normal situations
However, the programers here have already put in the print statements into thier stored procedures, and I am looking for a way to ignore the print statements - or possibly redirect them somehow, as when the stored procedures are run in production - it creates a great deal of chatter (verbose dialog) going to the workstation which greatly slows down the application.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply