Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm profiling a database just now and need to see the UPDATE and INSERT statements being executed on a particular table.

However, because the table has a 'Password' column the SQL Profiler is being understandingly cautious and replacing the TextData column with:

-- 'password' was found in the text of this event.
-- The text has been replaced with this comment for security reasons.

How do I prevent it doing this because I need to see the SQL statement being executed?

share|improve this question
up vote 1 down vote accepted
  1. Revert to sql server 2000 sp3
  2. Upgrade to sql server 2005
  3. Use this hack which PATCHES sqlservr.exe & definitely not supported by microsoft.
share|improve this answer
Oh joy. This is a production box and the bug I'm trying to trace only happens in production. Thanks anyway. – Kev May 26 '10 at 16:01
your only alternative is to rename any reference to password (or other bad words) in the call – Nick Kavadias May 26 '10 at 16:03
Yeah...Sadly there's no chance of doing that. The column is used all over the sodding place. Talk about security through obscurity. That's one of the worst approaches to solving a [non-]problem I've ever seen. I could go on..... :) – Kev May 26 '10 at 16:11
you're not the only one that thinks this:… – Nick Kavadias May 26 '10 at 16:13
added your other option... hahaha – Nick Kavadias May 26 '10 at 16:17

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.