The schema script 'CD_InTransit_v_153.sch' could not be propagated to the subscriber.
Error Detail:
The schema script 'CD_InTransit_v_153.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL20164)
Get help: http://help/MSSQL_REPL20164
Invalid object name 'dbo.Debit_v'. (Source: MSSQLServer, Error number: 208)
Get help: http://help/208
According to error message, it seems that debit_v is missing. However, I cannot control the sequence of view to replicate. How can I solve this problem
That's why we stopped replicating views and stored procedures.
We first subscribe (tables) and then run a script which creates views and SPs.
Occuring db-changes are quite easily: change them on the publisher, reinit all subscribers and after the first synch remove and recreate all views and SPs.
Might not be the most elegant solution, but it works (as long as you "know" your subscribers).
regards
Aline
|||So that is the nested view problem.. however, I just tried it on transactional with update replication.. everything goes fine. error only happens on merge replication.
Anyways, any other work around.. I really don't want to do any manual work. Any option that i can turn off so that it will not check reference view when create new view.
You might also want to look at using snapshot replication to deploy them.|||I should have mention that this happen for the first time replication to subscriber. So when apply the new snapshot to subscriber and got this error. Probably caused by nested view.
So, do you mean I manually copy all those snapshot file to subscriber pc and run them?
May be I dont' understand your answer. Can you give a little more detail on it? THX.. I am really newbie on replication. Please kindly help.
No comments:
Post a Comment