SecureFiles_v2.pptVIP

* * Creating SecureFiles You create SecureFiles with the storage keyword SECUREFILE in the CREATE TABLE statement with a LOB column. LOB implementation available in prior database versions is now referred to as BasicFiles. When you add a LOB column to a table, you can specify whether it should be created as SecureFiles or BasicFiles. If you do not specify the storage type, the LOB is created as BasicFiles to ensure backward compatibility. In the first example in the slide, you create a table called FUNC_SPEC to store documents as SecureFiles. Here you are specifying that you do not want duplicates stored for the LOB, that the LOB should be cached when read, and that redo should not be generated when updates are performed to the LOB. In addition, you are specifying that the documents stored in the doc column should be encrypted using the AES128 encryption algorithm. KEEP_DUPLICATES is the opposite of DEDUPLICATE, and can be used in an ALTER statement. In the second example you are creating a table called TEST_SPEC that stores documents as SecureFiles. For this table you have specified that duplicates may be stored, and that the LOBs should be stored in compressed format and should be cached but not logged. The HIGH compression setting incurs more work, but offers better data compression. The default compression is MEDIUM. The compression algorithm is implemented on the server-side, which allows for random reads and writes to LOB data, which can be changed via ALTER statements. The third and fourth examples above affect the same result: creating a table with a SecureFiles LOB column using the default AES192 encryption. * 38 2 1 The New Mexico State Highway and Transportation Department maintains an extensive database on its entire roadway system to facilitate maintenance, limit its legal liability, and qualify for federal roadway funding. State wide, images have been captured at every 50 feet of highway. Additional important information is associated with these images