Note: If you change dbdefence.dll or sqlboot.dll than digital signature of Active Crypt Software becomes invalid. It is not a problem, but some antivirus software MIGHT have another opinion on that.

If you rename dbdefence.dll it starts automatically. You do not need to create any extended stored procedures inside SQL Server.

There are several options and you would need to use binary resource editor. If you do not have any resource editor tool you can get one for free from www.ResEdit.net.

Renaming dbdefence.dll and real_sqlboot.dll

dbdefence.dll which is the key part of protection can be renamed to virtually any name you like. However if you rename dbdefence.dll you must change DbDefence sqlboot.dll to specify the new name. During installation DbDefence change original sqlboot.dll to it's own sqlboot.dll and rename the original to real_sqlboot.dll. You can change the name of real_sqlboot.dll as well.

Both files dbdefence.dll and real_sqlboot.dll loaded from sqlboot.dll. You need to edit resources of that file. If you do not have any resource editor tool you can get one for free from www.ResEdit.net.

Open sqlboot.dll with ResEditor and navigate to String Table. You should see something like this. If not, than probably you opened original sqlboot.dll from Microsoft. Check file properties and see copyright information

As you see there are two places for both files. You can change one or both. Filenames can be relative or absolute path.

Do not forget to press Save ! File must not be locked by running SQL Server instance.

Renaming .dbd_key extension

Open dbdefence.dll with ResEditor, navigate to String Table, find string with ID 500 and change it. By default alternative extension is .idx.

Renaming .key extension

If you purchased redistribution license or DbDefence you must have special key file valid for every server without activation. By default its name is dbdefence.key. You can change it as well.

Open dbdefence.dll with ResEditor, navigate to String Table, find string with ID 501 and change it. By default it is .key.

If you rename dbdefence.dll itself to, say, fence.dll the default key will be fence.key. You can change string with ID 501 to .xml and DbDefence will look registration information in file fence.xml