Hmm, D seems like the way to go. I wonder if there's a way to set a global default retention policy instead of doing it manually on each data extension? That would be a real time-saver.
I'd go with D. Applying the retention setting during data extension creation is a proactive approach, and it's less likely to be overlooked than manually configuring each one later.
D seems like the most straightforward way to handle this requirement. Applying a row-based retention on each data extension ensures the inactive data is cleared consistently across the board.
I think option C) Set inactive data to be automatically cleared after one year, but is recoverable, strikes a good balance between data retention and manageability.
Stanton
1 days agoEsteban
5 days agoDelfina
11 days agoGaston
13 days agoGerald
16 days agoEmilio
19 days agoFloyd
21 days agoRaymon
24 days ago