• Replies 5 replies
  • Subscribers 338 subscribers
  • Views 110 views
  • Users 0 members are here
Related

Purging Stale Customers

Sean Pinto
$organization

Hello,

  Has anyone had any success with purging (deleting) old and unused customers from their database?  Using some criteria we are considering deleting upwards of 200,000 customer records that have no ticketing, contribution, or informational history (mostly from our conversion 7 years ago).  I feel like there are a few tables with customer data that don't use have any referential integrity constraints.....  

Thanks for any info!

Sean

Parents
  • $organization

    Hi Sean,

    Just wandering what would be a reason to purge customers. If interested: to improve the overall database performance and its size we do purge and archive periodically the following tables:

    T_WEB_SESSION_VARIABLE:
    delete entries older than 5 days (in our environment, the table size would be several hundred million rows without the purge);

     T_WEB_SESSION_SESSION:
    delete and archive entries older than 2 months;

    T_ORDER_SEAT_HIST:
    for performances older than 1.5 year, for each seat preserve the latest transaction and archive/delete the rest; leave performances "younger" than 1.5 year intact.


    To asset tables contribution to DB size, please check out the attached DB procedure.

    If you need details, my direct contact is: SBasyuk@CarnegieHall.com

    Thanks,
    Simon Basyuk
    DBA, Carnegie Hall

Reply
  • $organization

    Hi Sean,

    Just wandering what would be a reason to purge customers. If interested: to improve the overall database performance and its size we do purge and archive periodically the following tables:

    T_WEB_SESSION_VARIABLE:
    delete entries older than 5 days (in our environment, the table size would be several hundred million rows without the purge);

     T_WEB_SESSION_SESSION:
    delete and archive entries older than 2 months;

    T_ORDER_SEAT_HIST:
    for performances older than 1.5 year, for each seat preserve the latest transaction and archive/delete the rest; leave performances "younger" than 1.5 year intact.


    To asset tables contribution to DB size, please check out the attached DB procedure.

    If you need details, my direct contact is: SBasyuk@CarnegieHall.com

    Thanks,
    Simon Basyuk
    DBA, Carnegie Hall

Children
No Data