You can set up FSA jobs to scan Oracle and SQL Server databases. Specifically, the FSA can scan columns in database tables that contain text or binary data. Binary data refers to documents (such as Microsoft Office files).
What Are Database Events?
When the FSA scans a database table, the scanned data is written to XML blob files. The FSA then passes these blob files to policy engines for processing.
Policy engines then apply Data At Rest triggers to the blob files. If a trigger fires, a database event is generated and stored on the CMS. You can search for these events in the iConsole.
Data At Rest control actions (such as deleting or replacing scanned items) are not applied to scanned database records.
How Does the FSA Create Database Events?
By default, all scanned data in the table (each column for every row) is written to a single XML blob file and stored as a single event. However, for very large database tables, this is clearly undesirable. Instead, you can configure the FSA to slice the scanned data into smaller, more easily manageable events.
For example, you can specify a maximum number of rows per event, or a maximum size (in KB) per event. You can also configure special handling for binary data; for example, if a database table contains MS Word documents, you can specify that these documents are stored as attachments to database events.
|
Copyright © 2014 CA.
All rights reserved.
|
|