In part 2, we talk how to collect some data and shrink our database. Here are the results.

After part 2, here are the numbers, with charts, to show how different areas of the system were affected. As a refresher, here are the companies we will be looking at:

AAA - All buy, make, sell, and retail sale operations in one legal entity with WMS processes. 12261 Purchase Order Lines per year, 497910 Sales Order Lines per year, 16797 PO Invoice lines per year, 491411 Sales Order invoice lines per year, and 569034 Ledger Journal Lines per year.

BBB - Purchases and manufacturing. sold via intercompany to CCC using WMS processes. 2965 Purchase Order Lines per year, 3641 Sales Order Lines per year, 3223 PO Invoice lines per year, 3561 Sales Order invoice lines per year, and 20255 Ledger Journal Lines per year.

CCC - General Ledger consolidation for BBB and DDD. 0 Purchase Order Lines per year, 0 Sales Order Lines per year, 0 PO Invoice lines  per year, 0 Sales Order invoice lines per year, and 33455 Ledger Journal Lines per year.

DDD - Sales and Retail sales using WMS processes. 10170 Purchase Order Lines per year, 782041 Sales Order Lines per year, 10500 PO Invoice lines per year, 765551 Sales Order invoice lines per year, and 459014 Ledger Journal Lines per year.

Raw Data

Here it is. We recorded sizes after each cleanup operation and these are the results. 

You can see our biggest decreease was in our financials only company, which makes sense and we'll highlight below. Next is our procurement and Manufacturing company. And in last place are companies that are heavy on sales.

Company AAA

Our biggest areas for reduction were GL Cleanup and cleaning up sales history. In a near tie for third where PO history clean up and Inventory dimension cleanup.

Company BBB

Since this company is mostly used for Purchasing with MRP and very little in the way of financials outside of the normal AP and MFG postings, we don't see much of a change when we run the GL Cleanup. However, PO history clean up and Inventory dimension cleanup are netting our most reducution. Also, it looks like space went up when cleaning up production order journals. I suspect this is because those tables were heavily logged so the additional space was from database logging and not an actual increase in space used by the production module.

Company CCC

Our only area for reduction were GL Cleanup. This makes sense as all this company did was financials and nothing else. 

Company DDD

Our biggest areas for reduction were GL Cleanup, cleaning up production order journals and Inventory dimension cleanup. This makes sense are those are the areas with the most activity ( mostly posted journals ) that we can clear out as they are more than likely no longer required. This company does all operations in one legal entity so we have a very mixed work load.