I am running a transactional replication with updatable subscriber. When a new record is inserted in one of the publisher tables, it assigns the next largest value to the identity column even if some of the previous records are deleted. For instance, if the records start with identity columns of 5 to 10. The next record will have 11.
However, in the subscriber tables, the next largest "available" value is assigned, meaning that the next insert command will have the identity column = 1 in this example.
How can I prevent the subscriber from doing so? I would like for it to instead act exactly like the publisher.