Previous Topic: Scanned File DatabaseNext Topic: Specify FSA Server Properties


Binary Data Handling

When setting up a database scanning job, you can specify special handling for binary data. For example, if a database table contains MS Word documents, you can specify that any documents found are stored as attachments to the resulting database event.

Binary data options

The following binary data options affect the events created by the FSA:

Example Database Table

In this example table, column C contains binary data (in this case, Microsoft Word documents of varying size):

 

Col.A

Col.B

Col.C

Col.D

Row 1

data

data

icon MS Word doc

data

Row 2

data

data

icon MS Word doc

data

Row 3

data

data

icon MS Word doc

data

Row 4

data

data

X

data

Row 5

data

data

icon MS Word doc

data

Row 6

data

data

X

data

Store Binary Data as Event Attachments = True

If you store binary data on the CMS as event attachments, the binary data options affect the events created by the FSA in the example database table as follows:

Only store database rows with columns containing binary data = True

Only rows with binary data are stored.

Store rows containing binary data as individual events = True

Only rows with binary data are stored and they are stored as individual events. The FSA generates four events:
Event1 contains data for row 1; plus attachment
Event2 contains data for row 2; plus attachment
Event3 contains data for row 3; plus attachment
Event4 contains data for row 5; plus attachment

Store rows containing binary data as individual events = False

Only rows with binary data are stored, but they are not stored as individual events. The FSA generates one event:
Event1 contains data for rows 1, 2, 3, and 5; plus four attachments

Only store database rows with columns containing binary data = False

All rows are stored.

Store rows containing binary data as individual events = True

All rows are stored, but rows with binary data are stored as individual events. The FSA generates five events:
Event1 contains data for rows 4 and 6
Event2 contains data for row 1; plus attachment
Event3 contains data for row 2; plus attachment
Event4 contains data for row 3; plus attachment
Event5 contains data for row 5; plus attachment

Store rows containing binary data as individual events = False

All rows are stored, but rows containing binary data are not stored as individual events. The FSA generates one event:
Event1 contains data for rows 1 through 6; plus four attachments

Store Binary Data as Event Attachments = False

If you do not store binary data on the CMS as event attachments, the binary data options affect the events created by the FSA in the example database table as follows:

Only store database rows with columns containing binary data = True

Only rows with binary data are stored.

Store rows containing binary data as individual events = True

Only rows with binary data are stored and they are stored as individual events. The FSA generates four events:

Event1 contains data for row 1; no attachment

Event2 contains data for row 2; no attachment

Event3 contains data for row 3; no attachment

Event4 contains data for row 5; no attachment

Store rows containing binary data as individual events = False

Only rows with binary data are stored, but they are not stored as individual events. The FSA generates one event:

Event1 contains data for rows 1, 2, 3, and 5; no attachments

Only store database rows with columns containing binary data = False

All rows are stored.

Store rows containing binary data as individual events = True

All rows are stored, but rows containing binary data are stored as individual events. The FSA generates six events:

Event1 contains data for row 1; no attachment

Event2 contains data for row 2; no attachment

Event3 contains data for row 3; no attachment

Event4 contains data for row 4

Event5 contains data for row 5; no attachment

Event6 contains data for row 6

Store rows containing binary data as individual events = False

All rows are stored, but rows containing binary data are not stored as individual events. The FSA generates one event:

Event1 contains data for rows 1 through 6; no attachments