Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
daunce
Starting Member
11 Posts |
 Posted - 2008-09-16 : 19:35:29
|
| Hi,I set up log shipping to run reports on another server, but now they want more up to date information.How quick can i get log shipping to commit to the report server? I think the default is 15mins, but what are the implications of having it every 3-5 minutes?ALso i read that when it goes to update the report server, it must disconnect all the current connections, so anyone running a report would get an error and have to run it again, which increases with the more frequent log shipping.If i choose not to disconnect users during the restore, will it do the restore the second it has no users, and is there a timeout period for it to realise there are no users? I'm just worried that it may be waiting for a long period of time before it can do a restore.I looked at transaction replication, but we have a primary and a mirror, and the transaction replication doesn't work with the mirror.(We want a primary, and failover mirror, and a report server)Any ideas? thanks. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-16 : 20:24:38
|
| Yes, that is drawback of Log shipping. If you choose other option to delay,then your secondary DB won't be upto date as logs are piled up.I would recommend Transactional Replication with it.We use Transactional Replication for Reporting purposes and it is working best. You can use Replication Monitor to watch replication. |
 |
|
|
|
|
|
|
|
How quick to ship logs?