Changed system date while replication running

  • We had some people doing daylight savings time testing while transactional replication was running.  The distribution agent "died" with the message "Difference of two datetime columns caused overflow at runtime".  Can anyone tell me what step in the replication process does this sort of datetime comparison?  Is there a way to work around it, i.e. delete entries using sp_MSDelete_PublisherDB_Trans?  Or is my best bet to simply re-initialize the subscriber?

    As a bonus question, what could have been done to prevent problems?  Would the only option be to shut down replication until the tests are complete, or would stopping and starting it for each date change have worked as well?


    Have Fun!
    Ronzo

  • This was removed by the editor as SPAM

  • Are you saying you changed the date of the system not that daylight savings time kicked in.

    Not sure what does the comparison but yes I would disable replication during the test and consider reinitializing snce you might have records left from testing in the transaction log that might throw it again.

  • Thanks!  Yes, the developers changed the system date to October to test the change of daylight savings time, then changed the date back again all while replication was running.


    Have Fun!
    Ronzo

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply