Skype Chat: Performance - April 9th

Caroline Barnes

Thank you to everyone who attended our Performance Skype chat this past week.  Attached are the summary and transcript of the session.

 

There were a number of action items following this session.  Len Wyatt promised a new index maintenance article which is now posted for us here in the community.

 

We had some questions about what the Global Change Process called "Business Process Output Delete" is.  I am working on updating our user guides with the following details but also wanted to share it with the community.  Here's what we've come up with:

 

1. Five different business process types' output is considered when running this process(you can create a selection for any combination of the 5 to include).  They are: Finder File Import Process, Segmented House File Import Process, Export Process, Correspondence Process, Marketing Effort Export Process.
2. In terms of export processes, there are many places throughout the system where we export results.  We're not just looking at tables generated by the "Export" processes run in the Administration functional area.  There are 5 types of processes with exported resuts that are cleaned up by this process: Receipting Processes, Generate Reminders Processes, Export Processes, Acknowledgement Processes, and Correspondence Processes.
3. There are some qualifications around the date specifications that we can select when we configure a process.  When we specify a date (such as "Delete output tables generated by business processes older than 10 days/1 year/2 months/etc.), we're actually going back not 10 days from the current date, but 10 days from the date that the business process was last run.  So, even after you run the global change, you may have tables older than 10 days in place (but not more than 10 days since the last time you ran the associated business process.

 

Subscribe to this topic for further updates!

Caroline Barnes

Quick update on this topic from our Products team:  

 

We had a question about what happens when a table is deleted - is the SQL table truncated, or dropped entirely from the backend?

 

Products has confirmed that the table that holds the output for that specific business process run/status is dropped entirely from the database.

Jeff Garmon

Caroline Barnes:

Quick update on this topic from our Products team:  

 

We had a question about what happens when a table is deleted - is the SQL table truncated, or dropped entirely from the backend?

 

Products has confirmed that the table that holds the output for that specific business process run/status is dropped entirely from the database.

Caroline,

 

Just wanting to verify I understand the date logic described in bullet #3 above.  I configure the delete output business process to delete older than 6 months.  

 

There is process which executes on the first of every month, has output in the system for 13 months; the global change will use the last executed time of that process, subtract 6 months from that last execution time; thus deleting the oldest seven occurrences of the output and leaving the most recent six months output available.

 

Another scenario, someone created an export for some vendor which ran 3 times a year ago all on the same day and none since; none of that output would be deleted because all the dates relative to the last process execution time are less than 6 months.

 

Am I understanding that correct?

 

Thanks

Jeff Garmon

University of Georgia

 

 

 

Caroline Barnes

Jeff Garmon:

Caroline,

 

Just wanting to verify I understand the date logic described in bullet #3 above.  I configure the delete output business process to delete older than 6 months.  

 

There is process which executes on the first of every month, has output in the system for 13 months; the global change will use the last executed time of that process, subtract 6 months from that last execution time; thus deleting the oldest seven occurrences of the output and leaving the most recent six months output available.

 

Another scenario, someone created an export for some vendor which ran 3 times a year ago all on the same day and none since; none of that output would be deleted because all the dates relative to the last process execution time are less than 6 months.

 

Am I understanding that correct?

 

Thanks

Jeff Garmon

University of Georgia

 

 

 

Hi Jeff!

 

That's exactly correct.  If you find that that's not the case in any instances or have any trouble with this, let me know.

 

Caroline

Caroline Barnes

Caroline Barnes:

Hi Jeff!

 

That's exactly correct.  If you find that that's not the case in any instances or have any trouble with this, let me know.

 

Caroline

Quick update to this issue: After speaking with Jeff further and doing some more testing, it seems that in some instances the global change runs based off of the current date, and in others it runs based on the date the process was last run.  I have not been able to identify the circumstances under which one occurs versus the other, so have updated Product Development with this scenario.  Stay tuned or subscribe to this topic for updates - I'll add further information as soon as Product Development has more information on this issue.

Caroline Barnes

Caroline Barnes:

Quick update to this issue: After speaking with Jeff further and doing some more testing, it seems that in some instances the global change runs based off of the current date, and in others it runs based on the date the process was last run.  I have not been able to identify the circumstances under which one occurs versus the other, so have updated Product Development with this scenario.  Stay tuned or subscribe to this topic for updates - I'll add further information as soon as Product Development has more information on this issue.

Update to the global Business Process Output Delete - this issue has been changed in version 4.0 so that in the future it will be based on the number of days from the current date (the date that we run the process) rather than the number of days from the last time the process was run.