11.0

It is desirable to place the database file on a fast hard drive (e.g., 15000 rpm/second). If MS SQL Server is installed

on the same computer with FlexiCapture Servers, it is desirable to use one hard disk for the %temp% folder of IIS and

the File Storage and another disk – for SQL database.

Database File

The process of increasing the database file may lead to a temporary decrease in SQL Server performance, so it is

recommended to specify in database properties in Autogrowth settings that a one-time increment of the database file

must be at least 100 MB.

Recovery model

To improve performance of SQL Server, it is desirable to use a Simple Recovery Mode for the database.

Rebuilding indexes

After long work of FlexiCapture, a significant increase in the size of database can be noticed. At the same time, more

than 50% of the space can be occupied not with data, but with the indexes in tables.

In order to decrease the size of database and improve performance, it is recommended that indexes should be rebuilt

periodically (e.g., once for every million pages processed). This operation should be performed on tables, which con-

tain data to be changed frequently. It is recommended to perform this operation от a regular bases for the Batch,

Document, Page, EventLog, Task, DocumentParameter and BatchParameter tables.

Estimating the size of File Storage

Most of the space in file storage is occupied by images being processed in the system. For each loaded file, its source

image is stored as the original; besides black-and-white image copies and image thumbnails are created. For color

images, color copies with quality loss are also created.

The level of quality loss is specified in batch type properties, in the Displayed image quality field.

To get a relatively accurate estimate of the file storage size, you can upload 10 typical images to FlexiCapture and

view the size of a file storage folder, in which the batch (<FileStorage>\<GUID>\project_<id>\0000-0999\<Batch Id>)

is stored.