Problem with using @@DBTS between the primary and secondary in an AG

60 Views Asked by At

I have a problem at ETL process.

I have an ETL process that uses rowversion field and had an issue, because the ETL process was using the source database which had become out of sync in an AG, so I read the rowversion data from the secondary node, and I have had unknown problems since the change was put into place. I can query @@DBTS on the source database (primary node) and see it moving right along, but when querying on the readable secondary node, I see two odd things. One the value is not moving at all, though I know it has moved looking at logs. Two it is a larger value than on the primary. I am starting to think that the value is not stored in the actual database, and if it is why would it not be synced with the primary? I tried changing the AG to synchronous just to see if anything happened and it didn't. Does anyone have any insight to this issue?

Thanks in advance.

0

There are 0 best solutions below