We have two SQL Server 2005 production DB at remote sites. Due to network bandwidth issue, we need to replicate these DBs (publishers and distributers) to central corporate SQL 2000 DB (subscriber for backup and possible reporting (and in rare case as a failover server).
We would start out with backup from SQL 2000 db restored on remote SQL 2005 DBs. When we have DB issue on remote 2005 DB, we want to restore it from central corp. 2000 DB backup. Since two DBs are replicating to central DB, we DO NOT want combined db back up data on restored remote 2005 db. We can restore the db and delete unwanted data before we turn on replication from this restored server. So, this is not a problem.
The real problem is how to avoid snapshot replication (during initialization) when we create a transaction replication on this restored server to avoid over writing data on the central subcriber sql 2000 DB
HELP!!
How to skip snapshot in Transaction Replication (from SQL Server 2005 to 2000)
tao84
Thanks!! That was correct Michael and Raymond. Basically, I had to uncheck the "initialize" checkbox on the last step of subscription wizard to prevent snapshot from being applied to the subscriber.
Thanks you all for your comments and suggestions!!
Beaver01
Javmuch
Hi Brad,
I believe the create subscription wizard provides the option of whether you want to "Initialize data and schema". Does this not work for you for some reason
-Raymond
blackwing