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

Starting DBDefence

To check installation you can use command:

exec master..dbd_status

It shows if DBDefence started or not, Error code (0 - no errors) and Autostart option (reg. key or file).  If autostart is not enabled, SQL Server will not be able to attach encrypted databases. Normally you need to have autostart enabled. However if you have troubles you can disable it.

Read more about Autostart in Configuration section.

You can start DBDefence manually with the command:

exec master..dbd_on

If DBDefence is started there is no way to unload it from SQL Server.

To check if DBDefence runs in Free Version mode you can use command:

exec master..dbd_reg_info

Free Version can be used in commercial projects freely. However, the Free Version has a limited database size of up to 77Mb. Read more about obtaining the full version.


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