Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Other: Capture hvr_integ_seq milliseconds

Brenda Barsness User

We are using HVR to capture change history on SQL Server(CDC), and using hvr_integ_seq it's only rounding up to the nearest second, and need it to report in milliseconds, because milliseconds is not available we are having to create work arounds.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Mark Van de Wiel User

    Hi Brenda,

    There are several ways to determine order for changes.:

    1. hvr_integ_seq combines LSN information with order inside a transaction guaranteeing alphabetic ordering for every integrate job. This is the best option to ensure order.
    2. hvr_integ_key provides the timestamp representation at integrate time represented as a milliseconds value. This value is guaranteed to be unique per integrate job but - given the ms precision - limits integration to 1000 rows/s.
    3. hvr_integ_tstamp provides the timestamp down to ms when the row was applied but is not unique.
    4. hvr_cap_tstamp gives the commit timestamp on the source, but is no more accurate than a second (partly driven by the general inaccuracy of commit timestamps in databases, not specifically SQL Server). This value is also not unique.

    Between these values I feel that we have plenty of options to determine order. Please let me know if you disagree.

    Thanks,
    Mark.