Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dkimbrell
Starting Member
9 Posts |
 Posted - 2012-03-13 : 13:49:27
|
| Scenario: Over the course of about 24 hours I add several views and tables to my publication as part of design development. After adding each view/table, I designate it as an article in my merge replication, then create a new snapshot. On my personal laptop, I synch with the server each time I do this so that I can work with the new view on my front end Access interface. When I synch, the new view/table is picked up on my machine with no problems.The other subscribers in my company are synching irregularly (they have pull subscriptions and synch anywhere from hourly to daily). Some of them have no problems, but others are somehow not getting the script to create the view and their synch stopps at an "invalid object" error which refers to one of the new views or tables I created. I can fix this by creating the missing view/table locally on their subscription, but this is a hassle and it should be happening automatically just as it is on my own machine.I'm trying to figure out why some subscriptions pick up the new views/tables and others do not, so that I can avoid this problem in the future. Does it have to do with sequence of events (create table, create snapshot, synch, repeat) as I do design development? Will a user get this error if he does not synch between say, 5 different snapshot creations on the publication? How do I avoid this "invalid object" error at synch and ensure that each subscriber is able to pick up the CREATE VIEW or CREATE TABLE scripts that I'm putting into the publisher? |
|
|
|
|
|
Why won't new Views not get added during synch?