Resolve data not moving from staging tables to PortraitDW database in Interaction Optimizer

Product Feature: Database


Data does not move from staging tables in Interaction Optimizer 5.6 after run of the PopulateDW SSIS task either scheduled or executed manually.


This is due to default value 2000 set in the DWPopulate.dtsConfig file.

 <Configuration ConfiguredType="Property" Path="\Package.Variables[User::IO_BatchCopySize].Properties[Value]" ValueType="Int32">

As the value is set to 2000, the script will not move the data until the total row count reaches to 2000.


UPDATED: July 31, 2017
The count 2000 is selected to save the machine resources from getting consumed frequently for writing data from the staging database to PortraitDW database.

In Production environment, lot of database transactions take place, hence the count 2000 is appropriate. For the Staging/Test/Development environment, the number of transaction is less as compared to the production, hence it can take long time for the script to run and move the data to the PortraitDW database.

Setting the IO_BatchCopySize in the DWPopulate.dtsConfig to 0 (zero) will make it the script run and move data to the PortraitDW database without considering number of rows.

Location of the File: \PST\Portrait Shared Server\SSIS\DWPopulate.dtsConfig  

<Configuration ConfiguredType="Property" Path="\Package.Variables[User::IO_BatchCopySize].Properties[Value]" ValueType="Int32">