Detect SQL Profiler in SQL Server

Question

0.00/5 (No votes)

See more:

Hi,

I am trying to avoid trace my sql query in SQL profiler.Some queries I run contain sensitive information: passwords, credit card numbers, etc so I want to know that, If SQL Profiler is runing then my sql query not run in VB.net

Thanks

Posted 17-Dec-13 1:55am

Member 10295956

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mike Meinz · Answer 1 · 2013-12-17T02:08:00

Solution 1

I entered the following into a Google search textbox:
Is SQL Server trace running?

The first result was this:
SQL Server: Determining Running Traces[^]

Posted 17-Dec-13 2:08am

Mike Meinz

Comments

Pablo Aliskevicius 17-Dec-13 8:10am

I get one record even when SQL Profiler is not running.

Mike Meinz 17-Dec-13 8:25am

Yes, Trace ID=1. That seems to run all of the time.

If the OP has sensitive data, it would be a best practice to encrypt it. Attempting to restrict access by exotic means (like checking for an SQL Trace) will not protect the data as well as encryption.

Pablo Aliskevicius · Answer 2 · 2013-12-17T02:08:00

You assume that SQL Profiler is your only risk.
This assumption is wrong.
What about Wireshark, or Fiddler? They can see queries on the wire.
Also, if the credit card information is stored unencrypted in a database, a malicious DBA can export it using Management Studio, and sell it to his favorite criminal.

Never, ever store unencrypted sensitive information in the database.
Never, ever store passwords in the database. Not even encrypted. Store a salted hash instead (salted: different users with the same password should get different hashes).

Hope this helps,
Pablo.