When we upgraded from 10.0 to 10.2 a new reporting database was created. What I found strange is we now have 4 different reporting databases, all around 40GB. Has anyone else experienced this?
One 10.0 we only had one and it was never as large as 40GB. Can anything be done to shrink these databases? I provided a screen shot of the files for a pilot database, the production database has 4 as well.
Did you by chance not point to an existing report database when deploying this
No, the consultants we had used to perform the upgrade had us create a new report database. This caused more issues for us because we had to move all of our custom SSRS reports over to the new database.
I wonder if it would be easy to just retry the report database deploy and then use a report moving tool to move those reports
Re-deploy a new report database from the admin console? Do you have the name of the tool by chance?
I’m not endorsing this…but since it’s a pilot environment, you have more wiggle room. If you deployed a new report database through the console after removing the existing (back up first and make sure you have your custom reports all backed up outside of the database), then it will create a new report database with all the stock reports. Then you could use a tool (report sync, just search this forum ) to migrate the custom reports from an intact report database location to the new one.
IF you don’t feel comfortable doing this, I’m sure other folks on here might have a better idea of why it’s creating large mdf files for a report database
I have noticed this now on two separate implementations of 10.2.700
All instances where we create a new reporting DB are getting 4 MDF files of 50MB each and one LDF of 2GB
Is this by design?
