Some background:
My company has a SQL Server 2005 db that was acting as a shadow database to a SQL Server 2008 production database both on different servers. A contractor just recently moved the physical location of the server containing the shadow database and reinstalled to a different location with a different IP address. Now these linked servers are not talking to each other. There may have been a quick way to fix this but a coworker ended up replicating the shadow db to get the data current. So far, so good as all of the data is now matching up.
However, now the SSRS reports which use the replicated database as their datasource do not want to populate the reports with this new shadow database. When one clicks on the report it just hangs. No data ever comes forth.
Solution:
I do not think that this is a SSRS issue as the SSRS files came up just fine prior to the replication. I am thinking that I need to configure the new database somehow. Anyone have thoughts on this type of issue?
My company has a SQL Server 2005 db that was acting as a shadow database to a SQL Server 2008 production database both on different servers. A contractor just recently moved the physical location of the server containing the shadow database and reinstalled to a different location with a different IP address. Now these linked servers are not talking to each other. There may have been a quick way to fix this but a coworker ended up replicating the shadow db to get the data current. So far, so good as all of the data is now matching up.
However, now the SSRS reports which use the replicated database as their datasource do not want to populate the reports with this new shadow database. When one clicks on the report it just hangs. No data ever comes forth.
Solution:
I do not think that this is a SSRS issue as the SSRS files came up just fine prior to the replication. I am thinking that I need to configure the new database somehow. Anyone have thoughts on this type of issue?