Has anyone ever the experienced the following when replicating a SQL Server DB (using the Enterprise Manager):
Upon replication, the server copies structure, and updates an existing data, but doesn’t append any new records. So anything added on the source DB that doesn’t exist in the destination db isn’t copied across?
Oddly enough, this seems to persist even if I delete the destination DB, and ask the replication to go to a new DB (named the same). If I replicated to a new DB of a different name, or if I shut down the local SQL Server service and restart it before the replicating, the problem goes away.
Is there some setting I’m missing? I generally ask the wizard to copy all objects, not to copy users & permissions, drop objects first, and overwrite all data.
this is why i stopped using the wizard. it’s flakey. it’s usually more trouble free to do a backup and then a restore on the destination db.
this is why i stopped using the wizard. it’s flakey. it’s usually more trouble free to do a backup and then a restore on the destination db.