Profiler Protection

Since version v2.8 DbDefence masks SQL statements issued inside protected databases. It does this in the way that SQL servers mask the security sensitive SQL statements CREATE LOGIN, OPEN MASTER KEY, and so on. DbDefence completely hides statements.

This protection works for statements running in the context of the protected database and does not mask statements from an unprotected database even if they address a protected database. For example, if your current database is a master database and you SELECT * from ProtectedDB..ProtectedTable, that statement will be visible because it was issued in the context of the master database.

You can allow Profiling if you set an option before encrypting the database: