BookmarkSubscribeRSS Feed
pcapazzi
Pyrite | Level 9

In our development environment we had the contact history table wiped clean and executions of campaign occurred much faster. I take this to mean that the publishing of the reporting data is impacted by the number of records we have in contact history (billions - spanning several years). 

 

I'm curoius if there's a best practice around archiving the contact history data at some point so it's impact on operations is minimized. 

1 REPLY 1
shill
SAS Employee
I have to admit I saw this post yesterday and have been thinking over why it would improve campaign execution times... do you have selection criteria that uses history? If so, having a partition on CONTACT_DT and always using a date range could be of considerable benefit.

As far as best practices go, this is more of an organization-by-organization decision based on campaign requirements (selection criteria use cases, as I mentioned above) and reporting and/or analytical requirements. Moving old records off to a data warehouse would allow you to develop historical reports (different from what I would consider your operational campaign reports that are run against the CDM). Creating some DI Studio jobs (or other ETL) to schedule this kind of housekeeping is probably your next task.

Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users

How to improve email deliverability

SAS' Peter Ansbacher shows you how to use the dashboard in SAS Customer Intelligence 360 for better results.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 875 views
  • 0 likes
  • 2 in conversation