SQL Replication Problem - References between Views and Tables
Hello experts,
I wanted to install a replication of a db between a productive and backup server.
So I made a backup of the current DB from the productive server and restored that on the backup server.
Since we already had a merge replication publisher on the productive server, on the backup server I created a subscription to that merge replication.
But when I started the synchronisation I received the following error:
************************
2009-02-13 10:21:41.888 The schema script 'Historie_25.sch' could not be propagated to the subscriber.
2009-02-13 10:21:41.997 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'Historie_25.sch' could not be propagated to the subscriber.
2009-02-13 10:21:41.997 Category:NULL
Source: Microsoft SQL Native Client
Number: 3729
Message: Cannot DROP TABLE 'dbo.Historie' because it is being referenced by object '_Historie'.
**************************
Now it makes total sense that you cannot drop a table when it's still referenced.
What can I do to resolve this problem?
I wanted to install a replication of a db between a productive and backup server.
So I made a backup of the current DB from the productive server and restored that on the backup server.
Since we already had a merge replication publisher on the productive server, on the backup server I created a subscription to that merge replication.
But when I started the synchronisation I received the following error:
************************
2009-02-13 10:21:41.888 The schema script 'Historie_25.sch' could not be propagated to the subscriber.
2009-02-13 10:21:41.997 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'Historie_25.sch' could not be propagated to the subscriber.
2009-02-13 10:21:41.997 Category:NULL
Source: Microsoft SQL Native Client
Number: 3729
Message: Cannot DROP TABLE 'dbo.Historie' because it is being referenced by object '_Historie'.
**************************
Now it makes total sense that you cannot drop a table when it's still referenced.
What can I do to resolve this problem?
Ted Bouskill
Have you considered 'Transaction Log Shipping'? http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.