PRINT stmts in stored procedures?

[sqlcasey]

Hi,

I have a question about PRINT statements - sometimes developers here overlook removing their PRINT statements from the stored procedures they write - what is the effect, if any, of these PRINT statements?

Most of the sp's the write are called from applications, so the end user would never see the PRINT output.

Thanx

 

[AlexCuse]

Just my two cents, but I think they are occasionally useful for debugging in Query Analyzer.

Alex


It's a magical time of year in Philadelphia. Eagles training camp marks the end of another brutal season of complaining about the Phillies.

 

[SQLDenis]

what I usually do is have a bit debug flag that i can set to 1

@Debug bit =0

if @Debug =1
BEGIN
PRINT 'SomeStuff'
END

That way the print only appears in Debug mode

Denis The SQL Menace
SQL blog:

http://sqlservercode.blogspot.com/

Personal Blog:

http://otherthingsnow.blogspot.com/

 

[genomon]

We had problems early on leaving PRINTs active - filled up logfiles & degraded performance. I usually comment them out until needed....

I have great faith in fools; self-confidence my friends call it.
-Poe

 

[mrdenny]

In SQL 2005 leaving in the print statements can cause problems depending on how you are calling the stored procedure.

If you have a stored procedure with a print statement, then a select statement SQL 2005 will return a null record set along with the print statement then the recordset with your data.

I've seen it do this with ADO via ASP as well as a .NET application using ADO to connect.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[sqlcasey]

Thanks, all