Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using auditing to track usage of some procs in the database. In the log I can see a record for the Procedure being run and, immediately afterwards,the SQL statement that is being run. The statement shows the parameter name rather then the value i.e. WHERE CaseId=@P_CaseId rather than WHERE CaseId =100

Now I know there was a hotfix for SQL 2008 (not R2) that made this happen:

Did this not get rolled into R2? Is there a different fix I can apply? Is there a workaround anyone knows?

share|improve this question
Just checking, but did you read the More Information section of that article? The fix only applies to certain situations (most, but not all). – Jon Seigel Sep 14 '12 at 16:49
I've tried both parameterization settings - but I'm on R2 where the behaviour seems to be the same, but there's no explicit fix for R2 (that I can see) so I'm confused. Was it not changed in R2? – Rikalous Sep 18 '12 at 10:53
I assume the fixed behaviour in 2008 would carry over to R2. I was just checking to make sure that none of the exceptions apply to your situation. – Jon Seigel Sep 18 '12 at 15:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.