May 27, 2008 at 11:48 pm
Hi All
We have a consolidated server that have 14 databases running different services on each database. Four of the databases uses Reporting Services.
We use/want to use database mirroring as a DR solution.
My question is how do I configure Database Mirroring with Reporting Services?
Can Report Servers databases be mirrored and how will the failover work, when it fail over to the standby server?
Any help would be highly appreciated.
A
May 28, 2008 at 12:28 pm
I have the same question. I was hoping we could modify the connection string in the Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config file and add the mirror server name to the connection string but the Dsn tag in this file is either encrypted or encoded! Ouch!
Has anyone else have any idea on how we could accomplish this?
Thanks.
June 6, 2008 at 4:34 am
Hi i've got a similar challenge.
I've restored the database(from server A(Primary)) onto server B(DR) - but haven't setup the mirrored relationship yet.
On Server B on setting up of RS config, i get the error that the database is not yet initialized - i assume thats because Rs detects that the restored db belongs to Server A.
now, i could go ahead and initialize it on Server B and probably resolve error on Server B.
my question really is, had it been mirrored and i make that initialization -on fail over what will the impact be. these machines will be part of a 24/7 solution and i would need to get architecture right 1st time as i may not have the luxury of significant downtime to change after its gone prod.
any advice, appreciated.
June 6, 2008 at 1:45 pm
First it sounds like you've restored your database to server B incorrectly for the setup of mirroring; when restoring your database you need to do it 'WITH NORECOVERY'.
Now because the database will be in a 'Restoring...' state, you won't be able to initialize Reporting Services on server B (can't write to a database that is in the 'Restoring...' state).
So I suspect that what we'll need to do is to write a script that would be run when the mirrored database comes online; it would need to initialize Reporting Services.
September 19, 2008 at 9:55 am
I have a similar problem with reporting services and biztalk. Currently i'm using the datasource connection string:
Data Source=myserver;Initial Catalog=mydb
I need to somehow put the failover partner in the connection string similar to the web.config connection string.
I am also having problems with BizTalk connection strings.
Mirroring is not working well for me regarding failover connection strings.
Web.config works fine but not biztalk or reporting services 🙁
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply