Exceptions are useful if you want to exclude a particular object from protection. Any object that is excluded from encryption will remain accessible. You can only define exceptions once at encryption time, although in future releases of DBDefence there will be possibility to define them dynamically.

Exceptions are particularly useful if you wish to use the Service Broker feature in your database. Read more in the Service Broker section.

It is possible to specify exceptions in command line database encryption tool dbecrypt.exe. The tool accepts the file with the list of object names with or without schema name in unquoted form (i.e. NO [ or ]). Example of the command:

dbencrypt.exe -s MSSQLSERVER -d db1 -p 123ABC -e exceptions.lst

exceptions.lst may contain table, stored procedures, views, UDF and other types object names.

Specifying MyTable or *.MyTable means that access to object called MyTable will be allowed in all schemas.

schema1.* will allow access to all objects in schema schema1.

You must specify object names in unquoted form. Each starting from new line