March 15, 2010 at 11:59 am
Some of our developers deployed TFS to a development server and it ended up becoming our "production" version on the dev box. Well, obviously we wanted to get it off of dev and moved to a production box. During the migration to prod, we backed up the ReportServer and ReportServerTempDB databases so they could be restored to the prod server and reports would be retained. Problem was, we already had ReportServer and ReportServerTempDB dbs on the production server that were being used by other apps as it is a shared database server. So, we created a ReportServerTFS and a ReportServerTFSTempDB db on the production box through the Report Server configuration tool and restored the backups to those. I then noticed that the ReportServerTFS database was being used properly but I kept getting an error saying the account that was supposed to access the database did not have access to "ReportServerTempDB". I was wondering why it would be trying to access that temp db since the configuration was set up to use "ReportServerTFSTempDB". I then figured out that there are many stored procedures in ReportServerTFS that have "ReportServerTempDB" hardcoded in them since it was restored from a backup of ReportServer on the dev box. So, my question is, do I need to modify all of the objects in ReportServerTFS that have ReportServerTempDB hardcoded and change them ReportServerTFSTempDB or is it OK to give the account used to access the database the appropriate permissions in ReportServerTempDB even though that would mean ReportServerTFS would be using ReportServerTempDB as it's temp database? I know Microsoft says the tempdb database must be related in name to the primary reportserver database but will I run into errors if I do it this way? Thanks in advance for any recommendations.
March 17, 2010 at 8:50 am
Did u initialize the services with proper .snk
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply