Guidelines for Partitioning Database

Overview

AVEVA Work Tasks stores application data in SQL Server. Important data cannot be destroyed due to analytical or legal requirements. Keeping the data in transactional database, results in alarming database growth. Though the latest database management system and hardware can handle large amount of data, it might still affect the performance of an application.

AVEVA Work Tasks can be used across different business domains. Based on the business requirement, workflows might run continuously, resulting in data table growth for a few tables. These tables are critical for the workflow engine. The alarming growth of these tables affects the performance of the application. Table partitioning capabilities provide an option to boost the performance, without affecting the other areas of the application.

The partitioning of the database is recommended for those business applications that run large number of workflow instances.

AVEVA Work Tasks uses Range Partition. Partitioning feature functions by moving data as follows:

• The completed workflow details to secondary partition.

• The running and active workflows to primary partition.

Special Note

The partition feature is available only on Microsoft SQL server versions and editions that support table partition feature. Refer to the Microsoft documentation to check the availability of the partition feature.

For more information on partitioning, see Partition Database.