I decide to start a new thread as this is a different issues and I didn't want it, or anyone to get lost with this.
I succesfully created merge replication. I frequently use the field type int autoincrement.
Here is the problem, when I push a publication to a subscriber the identity seed in the subcriber table is reset to 1. In other words, if there are 100 record in the subcriber table, when a user add a new record the identity seed starts add 1. There are no key issues as the key is tied up to the rowguid, but it just looks scary to see a record with the same int numbers. There is just to much maintenance involved to go check the tables created at the subscriber after replication since there are to many. Actually, I take that back. I don't think you can change the identity seed after the suscriber table has been created and merge replication is running.
Like always, thanks for your comments.
MW
I succesfully created merge replication. I frequently use the field type int autoincrement.
Here is the problem, when I push a publication to a subscriber the identity seed in the subcriber table is reset to 1. In other words, if there are 100 record in the subcriber table, when a user add a new record the identity seed starts add 1. There are no key issues as the key is tied up to the rowguid, but it just looks scary to see a record with the same int numbers. There is just to much maintenance involved to go check the tables created at the subscriber after replication since there are to many. Actually, I take that back. I don't think you can change the identity seed after the suscriber table has been created and merge replication is running.
Like always, thanks for your comments.
MW