Protect your SQL Server database from unauthorized access, modification and distribution! Hides schema!
 
Home    DbDefence Help - SQL Server Encryption Prev Next
About DBDefence
System Requirements
Installation
Configuration and Startup
DBDefence Configurator
Starting DBDefence
Database Encryption
Introduction
Encryption Tools
Exceptions
Database decryption
FIPS 140-2 Information
Database Access
Introduction
Using SQL commands
DBDefence Client DLL
Reporting Services Extension
Editing Database with SQL Studio
Service Broker Access
Backup, Distribution ...
Replication
Backup
Distribution
DBDefence SQL functions
dbd_listdb
dbb_on
dbd_reg_info
dbd_status
Sales questions
Purchase and support
Activation
Acknoledgements
DBDefence 2.4 Reference

Configuration

Please read this page attentively as it may affect your SQL Server instance. DBDefence Configuration tool lists all local instances which support SQL Servers.

DBDefence Configuration tool starts with higher privileges to be able to install dbdefence.dll into Binn folder of an SQL Instance.

Important: When you click on install or during any normal DBDefence install process, the tool renames original sqlboot.dll from Binn folder to real_sqlboot.dll to act as a backup and copies a NEW sqlboot.dll from the DBDefence installation folder. That special sqlboot.dll is responsible for the initial dbdefence.dll loading. If you update your SQL Server with newer Service Pack it will probably OVERWRITE the newly configured sqlboot.dll and DBDefence will stop loading. To re-enable loading toggle the 'Installed' flag on and off. Newer SQL Servers sqlboot.dll will be renamed to real_sqlboot.dll and DBDefence sqlboot.dll  will be copied instead. Sqlboot.dll from DBDefence distribution is significantly smaller then original (about 4 KB).

Alternative: You can use AppInitDLLs key in the registry to automatically load dbdefence.dll together into SQL Server. This method is not supported by Configuration tool, however dbdefence.dll is ready to be loaded in that way as well.  Read more about it in the distribution section. In this case it is more stable against SQL Server updates because substitution of sqlboot.dll is not required. However some security scanners and antivirus tool may flag a security warning and prevent loading.

Configuration tool will check for dbdefence.dll in Binn folder of each instance. It also checks for dbd_autostart in the registry in Setup section of the corresponding instance. For example here:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\dbd_autostart

If there is no key then the value is set to 0 (off). The Installation program turns it to 1 (on).

When you toggle Autostart, that key is switched from 0 to 1. This means that dbdefence.dll will start right at the SQL Server boot time. If installed, but not activated dbdefence.dll will loading anyway although it does not activate its features on the SQL Server.

Additionally dbdefence.dll checks for file dbd_autostart in its main directory. This is done to simplify distribution.

support@dbdefence.com
Copyright Elitude Software, 2009-2010