Welcome to our presentation regarding database cleanup in Exact Globe Ronald Voets  Productline Manager Exact Globe Dion B...
Welcome to participants Name Via Company Andre Speek LinkedIn Cane Bert van Vreumingen LinkedIn MT Support Broos Barella E...
Exact Globe needs an clean up solution in order to be able to support customers with large databases.  This is needed to k...
Agenda <ul><li>Why is clean up needed </li></ul><ul><li>What top X tables cause most of the disk space requirements and  o...
Why is clean up needed <ul><li>The growing database size requires more disk space to create and store backups </li></ul><u...
What top X tables cause most of the disk space requirements and  or performance issues <ul><li>GBKMUT  General Ledger Tran...
Existing solutions <ul><li>Clean up financial entry tables. In the general settings a setting is available to control this...
Possible solutions  <ul><li>Clean up completed MRP records (Gbkmut)  </li></ul><ul><li>Clean up/compress actuals </li></ul...
Solution 1: Why can we clean up completed MRP Records from past financial years <ul><li>Completed MRP records are not used...
Solution 1: How does the MRP clean up tool work <ul><li>A year needs to be defined until which completed MRP records will ...
<ul><li>No stock allocation can be used </li></ul><ul><li>No data for the to be deleted years is present in Invoices To be...
Solution 1: Current status <ul><li>People who participate in this webinar can get the script for testing purposes only. Th...
Solution 2: Clean up actuals – some ideas <ul><li>How should the actuals be cleaned </li></ul><ul><ul><li>Like in Exact Gl...
Solution 3: Use triggers to maintain balance tables <ul><li>Getting balances out of balance tables is a lot quicker than g...
Solution 4: Split up GBKMUT (MRP versus budget versus Actuals) <ul><li>Index structure can be tuned based on transaction t...
Solution 5: Customer specific indexes <ul><li>Exact Globe uses a standard index structure and is not tuned based on usage ...
<ul><li>Feedback and questions </li></ul>
Upcoming SlideShare
Loading in …5
×

Presentation On Clean Up MRP records in Exact Globe

2,036 views

Published on

Presentation used for a webinar hosted by Exact Software's product management for an external community of Exact Globe and MRP experts.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,036
On SlideShare
0
From Embeds
0
Number of Embeds
26
Actions
Shares
0
Downloads
49
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Presentation On Clean Up MRP records in Exact Globe

    1. 1. Welcome to our presentation regarding database cleanup in Exact Globe Ronald Voets Productline Manager Exact Globe Dion Brands Principal Customer Support
    2. 2. Welcome to participants Name Via Company Andre Speek LinkedIn Cane Bert van Vreumingen LinkedIn MT Support Broos Barella ExactForum Clear Solutions Clive Boulton Blog Exact Coen Hendriks ExactForum Yceland Dave Kickken LinkedIn Bluxs Henk Bangma LinkedIn Harvey Nash Henry Tel ExactForum Arrix Jan van veenendaal ExactForum DNW Oscar van Klaveren ExactForum Basiqdental
    3. 3. Exact Globe needs an clean up solution in order to be able to support customers with large databases. This is needed to keep performance on acceptable levels and to keep disk space and backup requirements within limits.
    4. 4. Agenda <ul><li>Why is clean up needed </li></ul><ul><li>What top X tables cause most of the disk space requirements and or performance issues </li></ul><ul><li>Existing solutions </li></ul><ul><li>Possible solutions </li></ul><ul><li>Feedback </li></ul>
    5. 5. Why is clean up needed <ul><li>The growing database size requires more disk space to create and store backups </li></ul><ul><li>The growing database size requires more powerful hardware </li></ul><ul><li>The growing size of certain tables causes performance to go down </li></ul><ul><li>Getting balances out of GBKMUT becomes slower over the years </li></ul>
    6. 6. What top X tables cause most of the disk space requirements and or performance issues <ul><li>GBKMUT General Ledger Transactions Budgets MRP transactions </li></ul><ul><li>Amutas Financial entry lines </li></ul><ul><li>Bacodiscussions Documents and attachments </li></ul><ul><li>Blobs Document copies </li></ul>
    7. 7. Existing solutions <ul><li>Clean up financial entry tables. In the general settings a setting is available to control this (amutas) </li></ul><ul><li>Clean up documents and attachments via CRM>Entries> Documents (bacodiscussions) </li></ul><ul><li>There is no need to clean up the blobs table for now. The blobs table stores a copy of the original print out, e.g. invoices, as an image. When using PDF (setting available in document settings) you can control the size of blobs. </li></ul><ul><li>BacodiscussionPictures will not be filled anymore as of product update 393 </li></ul>
    8. 8. Possible solutions <ul><li>Clean up completed MRP records (Gbkmut) </li></ul><ul><li>Clean up/compress actuals </li></ul><ul><li>Use triggers to maintain balance tables </li></ul><ul><li>Split up GBKMUT (MRP vs Budget vs Actuals) </li></ul><ul><li>Customer specific indexes </li></ul><ul><li>Other? </li></ul>
    9. 9. Solution 1: Why can we clean up completed MRP Records from past financial years <ul><li>Completed MRP records are not used anymore to process transactions </li></ul><ul><li>Completed MRP records are used on some overviews </li></ul><ul><li>If users want to view data from deleted years, they can check a backup where the data is still present </li></ul><ul><li>For a typical logistic customer 50% of the records in GBKMUT are MRP records </li></ul>
    10. 10. Solution 1: How does the MRP clean up tool work <ul><li>A year needs to be defined until which completed MRP records will be deleted </li></ul><ul><li>It will log who runs the tool </li></ul><ul><li>Define which kind of completed MRP records to delete (Sales orders, Purchase orders, etc) </li></ul><ul><li>It will clean up Gbkmut, Orhkrg, Orhsrg, Orhstx, Orkrg, Orsrg, Orstx, Banktransactions </li></ul><ul><li>It uses temporary tables to store what to delete </li></ul><ul><li>It will rebuild the indexes of the tables from which records are deleted </li></ul>
    11. 11. <ul><li>No stock allocation can be used </li></ul><ul><li>No data for the to be deleted years is present in Invoices To be Received (ITR) screen </li></ul><ul><li>Exact Globe release should be at least 390 </li></ul><ul><li>No open Sales Invoices can be present </li></ul><ul><li>No custom solution can be used </li></ul>Solution 1: Limitations of the MRP clean up tool
    12. 12. Solution 1: Current status <ul><li>People who participate in this webinar can get the script for testing purposes only. The script is supplied as is and is not supported by the support departments of Exact Software. </li></ul><ul><li>For feedbackquestions on the script you can mail Dion Brands (dion.brands@exactsoftware.com) </li></ul><ul><li>First Integration tests have been executed successfully by support experts </li></ul><ul><li>Script has been run on a few customer backups. Number of records in GBKMUT went down from 2.9 million to 2.1 million and from 10.9 million to 4.6 million respectively </li></ul>
    13. 13. Solution 2: Clean up actuals – some ideas <ul><li>How should the actuals be cleaned </li></ul><ul><ul><li>Like in Exact Globe for Windows and Globe for Dos (check conditions for open transactions, remove financial years and generate opening balance) </li></ul></ul><ul><ul><li>Archiving database (create a seperate database and move data to that database on a regular basis, financial years will be removed from the live database) </li></ul></ul><ul><ul><li>Should we clean actuals? </li></ul></ul><ul><ul><li>Or.... </li></ul></ul>
    14. 14. Solution 3: Use triggers to maintain balance tables <ul><li>Getting balances out of balance tables is a lot quicker than getting it from GBKMUT </li></ul><ul><li>By using triggers SQL Server will make sure the balance tables are consistent to GBKMUT </li></ul><ul><li>Getting balances out of GBKMUT is currently an issue for several overviews and functions </li></ul>
    15. 15. Solution 4: Split up GBKMUT (MRP versus budget versus Actuals) <ul><li>Index structure can be tuned based on transaction types </li></ul><ul><li>A clean up solution will still be needed </li></ul><ul><li>Disk I/O is spread across two tables </li></ul><ul><li>Improved query execution </li></ul>
    16. 16. Solution 5: Customer specific indexes <ul><li>Exact Globe uses a standard index structure and is not tuned based on usage </li></ul><ul><li>We cannot benefit from new index optimization features in SQL2005/2008, due to support of SQL2000 </li></ul><ul><li>We have limited knowledge on how indexes are used in customer environments (this is an ongoing project) </li></ul><ul><li>3 rd party optimization tools an option? </li></ul>
    17. 17. <ul><li>Feedback and questions </li></ul>

    ×