70
We are migrating GP2010 to GP2015 and working with the Management Reporter component. When trying to rebuild the Database, the TempDB space grows to 100 Gig and stops because we have filled up TempDB. On our 2010 version, we have a 10Gig drive and there are no issues. Does anyone have a good ideas as to the next step. Thanks, Patrick
I was able to get it to migrate from CU11 to CU 16 Over the weekend. After the clean up finished, I had a 26 Gig Database. For the completion of the migration process, it used a !20 Gig log file for the DM. I also scheduled log Shrinks. At the end of migration, there was a transaction that ran for 3 hours which made the tran log grow to 120. So a summary for my success.
1.Run a clean up of history as has previously been recommended.
2 Make sure you have a transaction log that can grow to your requirements on the Data Mart.
3 Make sure have ample Tempdb space.
The entire migration on a happy path took 7 hours.
Thanks again to everyone who responded.
Thanks everyone for their ideas. I have started over many times with this as my target system( MRCU16) has failed on the tempdb side or the log of the DM grows to 100. I have not had any tempdb issues after I ran the MR clean up based on this link. www.gpug.com/.../how-to-delete-management-reporter-history
What happens now is that the log file of the DM grows to 100 gig and fills up the drive. The Enterprise DBA team suggests breaking down the transaction but this is a Management Reporter task.
The size of the Management Reporter DB is 27 Gig. I also removed all of the un necessary companies....we are down to 3.
Does the clean up in the link above also remove the history? I thought that it did but maybe that is not the case. I have also thought about moving this from CU11 to CU15...Maybe the leap to CU 16 is not a good thing.
My next step will be to remove history from the viewer and retry. Thanks again everyone.
I'm having a little hard time to figure out exactly what you're trying to achieve here..
your original post was about migrating your MR 2012 from GP 2010 to GP 2015.. at this point we're not even talking about the Datamart.
Consider the DM as a temp container that holds your live GP data like a SSAS cube (but it's not) and refreshes them every 5 minutes (overkill).
When it comes to migrate the MR 2012 database (ManagementReporter) to a new server, your first step is to restore the backup on the new server and reset the encryption key for all the content (moving the MR DB from one server to another is documented here. Make sure to read the comments as well, since they contain some valuable information.)
I'd then re-install the connectors (DM or Legacy) and then connect with the MR Viewer and do some clean-up in the historical reports. If the clean-up process is impossible to complete because of the size of data, you may want to consider to run some SQL scripts to reduce the historical data directly from the tables (which is a whole different story)
PS: without knowing your exact configuration (old & new), it's hard to provide exact actionable items.
Hello, you seem quite knowledgeable about this.
Our DB is roughly 46 gig. We have two 100 Gig tempdb on the migrated server and the DM Log went to 100 Gig on my last upgrade. Based on my query below....does a basic clean up get me around such logging? The DM database is in simple mode. Most of the 46 gig is in the tables below.
| TABLE_NAME | TABLE_ROWS | RESERVED | DATA |
| Reporting.Data | 43577 | 26419040 | 26417800 |
| Reporting.ReportLineAccount | 36113879 | 8217024 | 8167072 |
| Reporting.ReportLineFinancial | 54364656 | 4506672 | 4484728 |
| Reporting.ReportRow | 8483229 | 865240 | 862808 |
| Reporting.ReportUnit | 1539099 | 284608 | 282824 |
I can confirm what Jake posted..
Ran into the same issue a few years back and had to start clean-up the historical MR reports first.. even that was pushing the transaction log of the MR2012 DB into using up all the disk space, though the MR2012 Database was in 'SIMPLE' recovery mode. We were only using the Legacy connector at the time and not the DM. The problem is the sheer amount of data that some companies can accumulate over the years by generating RM reports at will, not realizing that it fills up their database which can grow into the hundreds of GB quickly. Discipline is key in removing old unused reports and / or having a SQL job that would run routinely cleanup of the historical reports.
One thing you may want to try is add more 'tempdb' files to your SQL server to allow for more 'work' space to SQL. You can spread multiple tempdb files over various drives. They don't need to sit all on the same folder/drive location. Microsoft suggests actually to allocated as many tempdb files as the server has CPU's.. i.e. 2 CPU's with 4-cores should have at least 8 tempdb files allocated.
Are you trying to build the data mart database from scratch or are you trying to upgrade? I recommend checking the current size of the database. During an upgrade or when rebuilding, SQL can use up to 3-4 times that size in order to complete the process. You may need to add more drive space to get the process to complete. If you are trying to upgrade, you may want to first reduce the size of the ManagementReporter database by deleting old report versions. That can be done in the MR Report Viewer application. Upgrading from your current CU11 version to CU13 or higher should help with tempdb issues. MR changed the database schema with CU13 so that tempdb usage is lower. Your most recent reply seems to indicate that you tried doing this but you ran out of space again. I would try this approach:
-Use Report Viewer to delete old report versions until the ManagementReporter database is a reasonable size.
-Shrink the ManagementReporter database and log files in SQL.
-Remove the data mart integration from the MR Configuration Console.
-Stop the MR services.
-Delete the ManagementReporterDM database from SQL.
-Start the MR services and close the Configuration Console.
-Upgrade to CU16: mbs.microsoft.com/.../MROverview
-If you run out of tempdb space during the upgrade, you will either need to add more drive space or reduce the size of the MR database until you can complete the process.
-Deploy the data mart.
Are you using SQL Express? Do you mean your tempdb grew to 10GB? SQL Express has a 10GB limit.
#1
André Arnaud de Cal...
292,884
Super User 2025 Season 1
#2
Martin Dráb
231,760
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
