Welcome to our presentation regarding database cleanup in Exact GlobeRonald Voets Productline Manager Exact Globe

Dion Brands Principal Customer Support

Name Via CompanyAndre 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

Welcome to participants

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.

Agenda

Why is clean up neededWhat top X tables cause most of the disk space requirements and \ or performance issuesExisting solutionsPossible solutions Feedback

Why is clean up needed

The growing database size requires more disk space to create and store backupsThe growing database size requires more powerful hardwareThe growing size of certain tables causes performance to go downGetting balances out of GBKMUT becomes slower over the years

What top X tables cause most of the disk space requirements and \ or performance issues

GBKMUT General Ledger Transactions \ Budgets \ MRP transactionsAmutas Financial entry linesBacodiscussions Documents and attachmentsBlobs Document copies

Existing solutions

Clean up financial entry tables. In the general settings a setting is available to control this (amutas)Clean up documents and attachments via CRM>Entries> Documents (bacodiscussions)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. BacodiscussionPictures will not be filled anymore as of product update 393

Possible solutions

1. Clean up completed MRP records (Gbkmut) 2. Clean up/compress actuals3. Use triggers to maintain balance tables4. Split up GBKMUT (MRP vs Budget vs Actuals)5. Customer specific indexes6. Other?

Solution 1: Why can we clean up completed MRP Records from past financial years

Completed MRP records are not used anymore to process transactionsCompleted MRP records are used on some overviewsIf users want to view data from deleted years, they can check a backup where the data is still presentFor a typical logistic customer 50% of the records in GBKMUT are MRP records

Solution 1: How does the MRP clean up tool work

A year needs to be defined until which completed MRP records will be deletedIt will log who runs the toolDefine which kind of completed MRP records to delete (Sales orders, Purchase orders, etc)It will clean up Gbkmut, Orhkrg, Orhsrg, Orhstx, Orkrg, Orsrg, Orstx, BanktransactionsIt uses temporary tables to store what to deleteIt will rebuild the indexes of the tables from which records are deleted

No stock allocation can be usedNo data for the to be deleted years is present in Invoices To be Received (ITR) screenExact Globe release should be at least 390No open Sales Invoices can be presentNo custom solution can be used

Solution 1: Limitations of the MRP clean up tool

Solution 1: Current status

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. For feedback\questions on the script you can mail Dion Brands (dion.brands@exactsoftware.com)First Integration tests have been executed successfully by support expertsScript 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

Solution 2: Clean up actuals – some ideas

How should the actuals be cleanedLike in Exact Globe for Windows and Globe for Dos (check conditions for open transactions, remove financial years and generate opening balance)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)Should we clean actuals?Or....

Solution 3: Use triggers to maintain balance tables

Getting balances out of balance tables is a lot quicker than getting it from GBKMUTBy using triggers SQL Server will make sure the balance tables are consistent to GBKMUTGetting balances out of GBKMUT is currently an issue for several overviews and functions

Solution 4: Split up GBKMUT (MRP versus budget versus Actuals)

Index structure can be tuned based on transaction typesA clean up solution will still be neededDisk I/O is spread across two tablesImproved query execution

Solution 5: Customer specific indexes

Exact Globe uses a standard index structure and is not tuned based on usageWe cannot benefit from new index optimization features in SQL2005/2008, due to support of SQL2000We have limited knowledge on how indexes are used in customer environments (this is an ongoing project)3rd party optimization tools an option?

Feedback and

questions