Snapshot log overhead

From: <dpurrington_at_my-deja.com>
Date: Fri, 19 Nov 1999 15:24:45 GMT
Message-ID: <813q3n$pa2$1@nnrp1.deja.com>

What is the overhead involved with snapshot logs? To put this another way, at what point do snapshot logs become an unworkable solution? I'd rather not have to involve a third-party product (like SharePlex by Quest), although I will if I have to.

Obviously this has something to do with the number of tables replicated, the frequency of refresh, and the volume of data. Can anyone nudge me in the right direction here? I definitely don't want to significantly impact the master database, but the target database is for reporting purposes so timeliness is not critical. SharePlex replication (and products like it) seem more appropriate for a hot- standby, bidirectional, or disaster recovery solution.

Thanks,
Dave P.

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Nov 19 1999 - 09:24:45 CST