Hi folks! I've a merge replication setup b/w two servers. Published tables have columns (INT IDENTITY SEED 1 INCREMENT[NOT FOR REPLICATION]). Whenever i apply the SNAPSHOT, i have to run DBCC CHECKIDENT('table' RESEED) for each table at the subscriber twice, for the values in the columns are almost always greater than the ID-Seed value. For example the last Identity value in the column is 999 but whenever i insert a new row; i get error; couldn't insert duplicate value into the table. When i run the dbcc check i see the following message: "Checking identity information: current identity value '1', current column value '999'." Why do i need to run this script each time. Is it normal or i am missing any option while setting up replication? Another thing: Upon removing or altering a table requires a full snapshot. It's painful especially when subscribers are over the WAN and and large size publishers. There's an option while adding a Push-Subscriber(Don'tThe subscriber already has the schema, don't initialize the schema).Means that we can drop a replication; delete and alter published tables at both the publisher and subscriber manually and then add our subscribers back using this option. I've tested this and seems to work. If this is the case, why the heck there's any need to apply the snapshot? What are the conscequences if i use this strategy. I wanna know from the experts b4 i try this on my production db. Thanx in advance. Howdy!