| Support |
| Site Admin |
|
| |
| Joined: 12 Mar 2004 |
| Posts: 370 |
| Location: Omaha, NE |
|
|
|
 |
|
 |
|
What kind of maintenance can I perform on a database file with SQL Triggers on it?
1. The operating system will not allow you to perform a CLRPFM (Clear Physical File Member) command on your database file if it has a Delete trigger on it. A Delete trigger will be on the file if you chose to store the encrypted field values in an external file when defining it the Field Encryption Registry. If you want to remove all the records from the file, you should perform a mass delete through a programming language or use a SQL Delete command.
2. Do not rename or move a database file if one or more of its fields are activated in the Field Encryption Registry. In order to keep the Field Encryption Registry ?in sync? with the new file location, you should follow these steps:
a. Deactivate the field in the Field Encryption Registry.
b. Rename or move the database file object.
c. Change the entry in the Field Encryption Registry with the new file location.
d. Activate the field in the Field Encryption Registry.
3. Do not perform a CRTDUPOBJ (Create Duplicate Object) command with TRG(*YES) specified. This action would duplicate the triggers to the new object, which would confuse the Field Encryption Registry and the encryption processes. Data may be lost. |
|
