Deleting audit rows?

Former Member
Former Member $organization

We seem to have experienced a pretty significant increase over the last few months in the number of audit rows created for inserts and deletes on t_cust_rank. I'm seeing some accounts with dozens of inserts and deletes within a couple minutes in the middle of the same night. Initially I thought it may be related to the Membership Update Utility, which causes lp_customer_rank to fire, but we haven't changed our schedule or parameters so I don't know what would have caused the sudden uptick. Has anybody else experienced something similar?

The only apparent issue so far is that it's more challenging to find useful information on somebody's audit tab when one has to scroll through hundreds of t_cust_rank rows, especially considering that we're not currently using the ranking functionality, (though we may start.)

Related question: I assume it would not be a best practice to modify the triggers on t_cust_rank. Is it safe to periodically delete the t_cust_rank rows from the audit table?

Parents
  • Please remove this email address from this list.

    Thank you.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matthew Echert
    Sent: Wednesday, August 12, 2015 4:14 PM
    To: Glutting, Keith <Keith.Glutting@metmuseum.org>
    Subject: [Tessitura Technical Forum] Deleting audit rows?

     

    We seem to have experienced a pretty significant increase over the last few months in the number of audit rows created for inserts and deletes on t_cust_rank. I'm seeing some accounts with dozens of inserts and deletes within a couple minutes in the middle of the same night. Initially I thought it may be related to the Membership Update Utility, which causes lp_customer_rank to fire, but we haven't changed our schedule or parameters so I don't know what would have caused the sudden uptick. Has anybody else experienced something similar?

    The only apparent issue so far is that it's more challenging to find useful information on somebody's audit tab when one has to scroll through hundreds of t_cust_rank rows, especially considering that we're not currently using the ranking functionality, (though we may start.)

    Related question: I assume it would not be a best practice to modify the triggers on t_cust_rank. Is it safe to periodically delete the t_cust_rank rows from the audit table?




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • Please remove this email address from this list.

    Thank you.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matthew Echert
    Sent: Wednesday, August 12, 2015 4:14 PM
    To: Glutting, Keith <Keith.Glutting@metmuseum.org>
    Subject: [Tessitura Technical Forum] Deleting audit rows?

     

    We seem to have experienced a pretty significant increase over the last few months in the number of audit rows created for inserts and deletes on t_cust_rank. I'm seeing some accounts with dozens of inserts and deletes within a couple minutes in the middle of the same night. Initially I thought it may be related to the Membership Update Utility, which causes lp_customer_rank to fire, but we haven't changed our schedule or parameters so I don't know what would have caused the sudden uptick. Has anybody else experienced something similar?

    The only apparent issue so far is that it's more challenging to find useful information on somebody's audit tab when one has to scroll through hundreds of t_cust_rank rows, especially considering that we're not currently using the ranking functionality, (though we may start.)

    Related question: I assume it would not be a best practice to modify the triggers on t_cust_rank. Is it safe to periodically delete the t_cust_rank rows from the audit table?




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
No Data