We have publisher A (sql 2016), distributor B (sql 2019), and subscriber C(sql 2016) in our env and each resides in its own vm box. The subscription in the subscriber is a pull one. We are using the transactional replication. I like to understand when a pull subscription is trying to get the data changes(commands) from the distribution db:
1. how does the subscription process determine where the starting point from previous successfully sync to get the next batch of commands in the dist db?
2. Does the subscriber have any replication system tables residing locally that would store some kind of record seq no so it knows the last successful sync point?
OD
Ocean Deep