![how to purge microsoft dynamics pos 2009 database how to purge microsoft dynamics pos 2009 database](https://images.slideplayer.com/30/9516093/slides/slide_12.jpg)
This will return the top tables in your Dynamics AX implementation by size.
#How to purge microsoft dynamics pos 2009 database download#
Another consideration would be to download the Dynamics Performance Analyzer and run the INDEXES_BY_SIZE portion of the 4-Analyze_SQL_Indexes script. If that is the case then you probably don’t need to purge data from the AIFDOCUMENTLOG and AIFMESSAGELOG tables. For example, you may not even be using AIF/Services or have logging turned on for it. Do we need to purge data from theses tables? To answer this I typically recommend evaluating if you are using these tables.If you setup Dynamics AX to log if someone updates a customer record then when a user accesses the custtable and updates a record there will be an entry in the sysdatabaselog table.įor these tables you should determine the answer to the following questions: SYSDATABASELOG – this contains records for instances in which a person accessed a table in which logging has been setup.Every time a batch job runs information about the start time, end time, status of the batch job, and infolog messages (if there were any) are stored. BATCHJOBHISTORY & BATCHJOB & BATCHHISTORY – these tables contain information about batch jobs that have run in the system.However, after time you can accumulate thousands of records and take up unnecessary disk space. This information is great to have if a service call has any issues. AIFDOCUMENTLOG & AIFMESSAGELOG – these tables contain information about AIF/Services calls that have been received by the system.However, a few tables that contain system data are low risk/low impact to purge on a regular basis. In this case, depending on how many batch jobs you have, you can accumulate a lot of information about past batch jobs. After a certain time frame, knowing for example, that a batch job completed successfully is not necessary information for you to have.
![how to purge microsoft dynamics pos 2009 database how to purge microsoft dynamics pos 2009 database](https://2.bp.blogspot.com/-6qwfzJjYK6E/WBv5XXspnOI/AAAAAAAAAOY/uNlGfaMHyY8znCiEmANx9H1OJCDH2MFBQCLcB/s1600/Mac_Repair_iMac_Macbook_aApple_Recovery-MAC-OS-X-Windows10-CS6-CS5.5-Photoshop_cc-Key-.jpg)
The reason is that they are what I would consider log tables of events that happened at some point in time in the system. The first topic is related to tables that I often recommend the customer considers purging data from. Since there is a lot of information out there related to SQL Server and Dynamics AX performance I wanted to start with a couple non-SQL Server topics. In this ‘ Top Tips for Microsoft Dynamics AX Performance Optimization’ series, I will be covering some of the items that I look for when analyzing the health of a Microsoft Dynamics AX system. These patterns have become things I look for when analyzing the health of client’s Dynamics AX systems. Which Microsoft Dynamics AX system logging tables should have a data retention policy?Īfter working with Microsoft Dynamics AX for over 10 years, you start to see patterns in issues that arise.