Setting up Unica Campaign to use database load utilities
You can improve performance by using a database load utility for all datasources.
About this task
Unica Campaign supports the use of database load utilities, which are available from your database vendors. You must obtain licensed copies of any database load utilities.
Database load utilities can improve performance when pushing ID lists into temporary tables and when exporting data from Unica Campaign to the database. For example, data is exported during a Snapshot, Mail List, or Call List process.
Load utilities can provide significant performance improvements. Testing on DB2® indicates that without the load utility, insertion of a million rows requires about 5 times more CPU utilization and significant disk I/O. Results vary depending on the hardware in use.
Procedure
To set up Unica Campaign to use a database load utility, there are three main steps to perform for each datasource: Create two load control file templates; create a script or executable to start the load utility; then set the loader configuration properties in Unica Campaign.
- Create two load control file templates.
Most database load utilities require the use of a control file. Unica Campaign can generate control files dynamically based on control file templates that you create.
- Create a script or executable to start the load utility.
To invoke the load utility, Unica Campaign uses a shell script (or an executable, for )Windows, which is identified in the Loadercommand configuration property. You can specify either a direct call to the database load utility executable or a call to a script that launches the database load utility.
-
Set loader configuration properties in Unica Campaign.
The loader configuration properties identify the control file templates and indicate the location of the script or executable file. Be sure to adjust the configuration settings for each data source.
Results
Unica Campaign performs the following actions when it writes to the database: First, it creates a temporary data file as fixed width or delimited text. If specified by the LoaderControlFileTemplate property, a temporary control file is created dynamically based on the template file and the list of fields to be sent to the database. Next, it issues the command specified by the LoaderCommand configuration property. Finally, it cleans up the temporary data file and control file.