Reporting Services DB Best Practice.

Ok, so, I see in an early post, that I need to ask a bigger question.
I have a production SQL 2005 Standard Server. I have another SQL 2005
Standard server that is used for reporting services only. What is the best
method for updating that reporting services DB on a 15 - 30 minute cycle.
The database should be read-only, but I do need to set different permissions
on it.
What's the best practice?
Mirror
Replication
Log ShippingHi,
Best option is "REPLICATION". depending on your need it should be
"Transaction Replication" for online reports. Instead of 15 min, go for
online transaction replication only.
In fact we use the same setup and transaction replication works absolutely
fine.
Amarnath
"Kevin Antel" wrote:
> Ok, so, I see in an early post, that I need to ask a bigger question.
> I have a production SQL 2005 Standard Server. I have another SQL 2005
> Standard server that is used for reporting services only. What is the best
> method for updating that reporting services DB on a 15 - 30 minute cycle.
> The database should be read-only, but I do need to set different permissions
> on it.
> What's the best practice?
> Mirror
> Replication
> Log Shipping
>
>|||I'm confused. What are you trying to do. Are you trying to have a hot
backup? You are not talking about the data that is being used in the report
but the report server databases?
I think you are making this harder than necessary if the purpose is a hot
backup. If one server goes down and the other comes on-line, the only thing
you will lose are whatever new subscriptions that have been setup since the
last time you synced the servers. Seems to me that doing that nightly would
be good enough. First, the chances are low you even need to even use this
(assuming you have normal fault tolerant hardware). Two, it is not a
transaction system where valuable data is lots. In the unlikely event the
server crashed then the users would have to recreate any new subscriptions.
If you are using report builder then the chance for some lost work is
higher. But still, weighing the complexity and the effort versus the gain.
I agree with the other post that if you have to do this that you are talking
replication, there are a variety of ways to do this (log shipping etc). SQL
Server 2005 has more options in this area than 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:u86ZH0DRGHA.5500@.TK2MSFTNGP12.phx.gbl...
> Ok, so, I see in an early post, that I need to ask a bigger question.
> I have a production SQL 2005 Standard Server. I have another SQL 2005
> Standard server that is used for reporting services only. What is the
> best method for updating that reporting services DB on a 15 - 30 minute
> cycle. The database should be read-only, but I do need to set different
> permissions on it.
> What's the best practice?
> Mirror
> Replication
> Log Shipping
>