Please backup the registry before performing below steps. I will assist you to delete the run history in Windows 10. The troubleshooting steps of Windows vista may not be applicable to solve the problems in Windows 10. Please be informed that, the link you have provided in the post is applied to Windows vista. But if it took 20-30 minutes for you, I'd say that I'm looking at twice that, maybe.We appreciate you for being a part of Windows 10. Those 16.2 million rows are spread amongst 328 Repository reports. I last cleaned it out about two months ago. Just checked ours: 16.2 million rows after about 3 months-worth of reports. I noticed that your ReportLineTransaction table had only 8.3 million records in it. So, instead of deleting the ReportLineTransaction records first, as my script does, Sandness's script goes for the Repository first, then whacks the Report table. The script suggests that both the Repository and Report tables have enough referential integrity to take care of a pretty deep hierarchy of dependent tables.
You said in your Dynamics Community post that the script took 20-30 minutes.
Since the script is cursor-based, I presume that it's going to be fairly slow. Is that common to use a different schema for the Repository? I see that our MR database includes tables in a "Connector" and "Schduling" schema, but not "Reporting".
CreateDate <= now we know the number of rows that will be deleted from the biggest table. We set a cutoff date for reports older than 30 days, and then count the number of rows in the ReportLineTransaction table for all the reports generated before the cutoff:ĭECLARE datetime = DATEADD ( day, - 30, GETDATE ()) Here’s how we do a rough calculation of how much data will be deleted. In the last quarter of the year, we’re adding about 4.5 GB of data to the database each month. By fiscal year end, some of these reports add over 600,000 rows to the ReportLineTransaction table in the ManagementReporter database. And the reports are generated down to the Transaction level. These reports get larger as the fiscal year marches on because they show progressively more and more data until there’s 12 months’ worth. In our company, we run a suite of specialized P&L reports at month-end.
0 kommentar(er)
