indianscorpion29 (10/20/2014)
We are also in the midst of implementing a merge replication solution in our company and we encountered the same issue.There should be a column in the table with some specific properties like it should be an identity colum, row GUID properties, not exactly sure but you can refer to google.
If such a colum does not exist, SQL will create the column with a default range of identity values.
What we did was, we got back to the developers and asked them to have a redundant colum in each table participating in replication with those properties and after that, While setting up the publication, I manually bumped up the identity range value to 10 million for each table being replicated.
Did not see this error after that.
Hope this helps.
Thanks for help.With your comment i still have something to research 😀
Look like problem "The schema script 'vwBuyADT_513.sch' could not be propagated to the subscriber." is really hard to solve. Is there anyway to skip that error :w00t:
One more thing, that i'm trying to merge databases that have around 200-500 tables.. If i manually imcreate identity range of theme, it would be crazy for me :w00t::w00t::w00t:
I changed indentity range to 100 Million for each table. Lets see after 12hours :D.
Again, thank you 🙂