Best option for reporting database

I have a SQL server with a lot of stress on it and I want to get the load
from reporting services of this database. So I need to replicate the database
to another server.
The maximum latency for my reports is 15 minutes so I think mirroring with
snapshots is not an option.
Another possibility is log shipping but what whit my log backups? And what
with the load replication is causing on my database server?
Any advice is appreceated.
Regards
That depends on your load. I would use transactional replication. You may
see a 5% increase in cpu utilization.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Zekske" <Zekske@.discussions.microsoft.com> wrote in message
news:A7F65ED4-75D4-4BFE-9EFE-C0959DFFF518@.microsoft.com...
>I have a SQL server with a lot of stress on it and I want to get the load
> from reporting services of this database. So I need to replicate the
> database
> to another server.
> The maximum latency for my reports is 15 minutes so I think mirroring with
> snapshots is not an option.
> Another possibility is log shipping but what whit my log backups? And what
> with the load replication is causing on my database server?
> Any advice is appreceated.
> Regards
|||Log backup's do not consume too much of CPU. So you can think of Log Shipping
too...
"Zekske" wrote:

> I have a SQL server with a lot of stress on it and I want to get the load
> from reporting services of this database. So I need to replicate the database
> to another server.
> The maximum latency for my reports is 15 minutes so I think mirroring with
> snapshots is not an option.
> Another possibility is log shipping but what whit my log backups? And what
> with the load replication is causing on my database server?
> Any advice is appreceated.
> Regards