15
As mentioned, the first step is to analyze which tables consume most space. Please check it (Disk usage by top tables report in SQL Server) and see if most of the space is consumed by history/log/alert data that you could simply delete instead of archiving.
Don't hesitate to share more details with us if you are unsure.
Hi Satish ,
Thanks for the reply. The problem is the production database size is 1 TB. And we have 10 non production environment including dev enviroments. The replication of this huge database is always becoming a hectic towards refreshing other enviroments. We intended to archive only SO and PO entities data and cannot archive GL data since Mgmt reporter is connected with Production Database.
Based on that, what do you suggest if we use IDMF tool since we are on Ax2012 R2 CU6. Does IDMF has any limitations for R2?
Hi Fahad,
The first task would be to identify the source of the problem. For e.g. what are your top 20 tables and how those tables get populated. E.g.batch history might be consuming lot of DB size. Are there tables that you just don't need and can truncate after analysis and careful consideration (can always back up separately).
There are lot of clean up jobs on respective modules, take a look at those.
Then look at standard tool that MS orders and see if that help alleviate some problem.
Last option would be to custo route.
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,432
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
