LS Retail - Replication Counters - sometimes transactions get skipped

• This can happen if the replication counter values on the records get changed in a way that causes a gap between numbers. Usually happens when a machine is repurposed, and old transactions are not fully purged, causing replication counter numbers to do unpredictable things
• Check the replication counter field in the transaction header by day by terminal and compare to the pos db to confirm if the numbers make sense

  select * FROM [GFH].[dbo].[Cronus$Scheduler Replication Counter$5ecfc871-5d82-43f1-9c54-59685e82318d]

  where [Scheduler Job ID] in ('TRANSKJB','TRANSMSQ')

SELECT [POS Terminal No_], MIN([Replication Counter]) AS FirstReplCounter, MAX([Replication Counter]) AS LastReplCounter, [Store No_]

FROM     [Cronus$Transaction Header$5ecfc871-5d82-43f1-9c54-59685e82318d]

GROUP BY [POS Terminal No_], [Store No_]

SELECT TOP (1000) [POS Terminal No_], MIN([Replication Counter]) AS FirstReplCounter, MAX([Replication Counter]) AS LastReplCounter, [Store No_]

FROM     [Cronus$Trans_ Sales Entry$5ecfc871-5d82-43f1-9c54-59685e82318d]

GROUP BY [POS Terminal No_], [Store No_]