Change Details

I'm interested in seeing us make the Silverpop export leaner. I know it takes a few hours for the export job to run, and it takes about an hour to import into Silverpop, during which time no other data jobs can run (like sending a mailing). I wanted to suggest what seems like an easy fix to cut way down on the job size. The solution: only send rows with values that have been updated in the last 48 hours. That will bring the row count down from over 11 million to what must be less than a few hundred thousand. Additionally, this will address a problem we have: we can't perform normal data hygiene and purge undeliverable addresses from our database, because the Civi job re-adds them to Silverpop each day. This prevents us from getting accurate list counts which impairs our projections.

I'm interested in seeing us make the Civi to IBM export leaner. It currently exports over 18 million rows of data every night. Every Big English, the export job ends up failing a few times, I think partly because the file is just so big. It also takes a long time to run the import on the IBM side, during which time no other data jobs can run (like sending a mailing). The solution: in the nightly export from Civi, only export rows with values that have been updated in the last 48 hours. That will bring the row count down from over 18 million to what must be less than a few hundred thousand. Additionally, this will address a problem we have: we can't perform normal data hygiene and purge undeliverable addresses from IBM, because the Civi job re-adds them to IBM each day. This prevents us from getting accurate list counts which impairs our projections.

I'm interested in seeing us make the Silverpop export leaner.Civi to IBM export leaner. It currently exports over 18 million rows of data every night. Every Big English, the export job ends up failing a few times, I know it takes a few hours forI think partly because the export job to run,file is just so big. and itIt also takes about an hour to long time to run the import into Silverpopon the IBM side, during which time no other data jobs can run (like sending a mailing). I wanted to suggest what seems like an easy fix to cut way down on the job size. The solution: in the nightly export from Civi, The solution: only sendexport rows with values that have been updated in the last 48 hours. That will bring the row count down from over 1118 million to what must be less than a few hundred thousand. Additionally, this will address a problem we have: we can't perform normal data hygiene and purge undeliverable addresses from our databaseIBM, because the Civi job re-adds them to SilverpopIBM each day. This prevents us from getting accurate list counts which impairs our projections.