|
In-database optimization is not supported for all databases. Your Campaign administrator can confirm whether this option is available for your data sources.
|
|
what operations are done at the database level or the local Campaign server level; and
|
|
In-database optimization prevents IDs from your database from being unnecessarily copied to the Campaign server for processing.
|
|
Some functions are still performed on the Campaign server, when necessary. For example, to calculate a derived field, Campaign first evaluates the derived field formula to see if any part of the calculation can be performed using SQL. If simple SQL statements can be used to perform the calculation, then the calculation is done "in-database". If not, then temporary tables are created on the Campaign server to handle the calculations and persist the results from process to process within a flowchart.
|
|
All raw SQL custom macros must begin with select and contain exactly one from in the rest of the text.
|
|
For databases that support only insert into <TempTable> syntax, you must map at least one base table to the same data source at the same audience level as the raw SQL custom macro. If the fields selected by the raw SQL custom macro are too large for the fields of the temp table, a runtime error will occur.
|
Copyright IBM Corporation 2015. All Rights Reserved.
|