SQL Server Profiler suddenly says Encrypted Text

Question

Recently I noticed that a stored proc we are trying to profile failed to appear in the profiling output.

After adding in SP:StmtStarting and SP:StmtCompleted events, I noticed the TextData reported as

-- Encrypted text

.. but the stored procedure is not encrypted.

This has only recently started happening - we used to profile this SP perfectly fine, and I can't figure what has changed.

Any suggestions would be gratefully received.

UPDATE: The SP is definitely not encrypted. I've created new SP's on the box, and I see SP:BatchStarting event with the new SP's name. With the old SP, I don't see the BatchStarting event, but I do see the statements within the SP executing.

However I need to see the values of the parameters the SP is being called with, as they are table types. Originally I could see the table types being instantiated and populated before the SP is called.

Answer 1

So I figured this out in case anyone finds it useful.

I have table type parameters to this stored procedure. One of the parameters is passed a lot of data (i.e. a C# DataTable with >5000 rows). Without this quantity of data the stored proc profiled fine.

I guess there must be some cut-off at which point Profiler does not show all of the data being passed in.