| Type: | Information | ||||||||||
| Summary: | |||||||||||
| This article explains how to allow SQL Server to access encrypted databases located on a RAW volume.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, read the Microsoft Knowledgebase article MS KB256986 Description of the Microsoft Windows Registry. |
|||||||||||
| Additional Information: | |||||||||||
In order to preserve resources, Encryptionizer by default comes with RAW volume access disabled when running on NT, 2K or XP.You can enable RAW volume access by modifying the following DWORD registry Value:
HKLMSYSTEMCurrentControlSetServicesnlemsqlInclude This DWORD value has the following meaning:
To specify more than one device, add the two values together. For example, to process encrypted files on local drives and RAW volumnes, specify 0x00011. If omitted the default is 0x0003 (local drives). However, if you specify a value, you must specify all devices that may have encrypted files on them, not just the additional devices. For example, if you specify 0x0010, then only encrypted files on RAW volumnes can be accessed. After changing this registry value, you must reboot the server in order for the change to take effect. Note that this affects dynamic encryption only. It does not affect file APIs such as N_ENCODEFILE, N_DECODEFILE and N_RECODEFILE. |
|||||||||||