PRINT - performance cost

Hi,

Does anyone know the cost of calling PRINT in terms of performance? Or where to find info on this matter?

I use PRINT mainly for debugging, and I am used to VC++ where the a TRACE isn't called in release builds. Is there a way of doing this in SQL Server 2000, or is it done automatically?

/PeterHow often are you using it? I mean, if you stick it in a loop that executes a million times MAYBE there would be a performance hit, but otherwise I can't see it making a big difference.

blindman|||No, not a million times but a good few thousands.

My experince is that TRACE/PRINT commands generally are very slow. Not so in SQL SERVER? But they are still called synchronously, right?