Skip to main content

Syncing Large Companies Downstream in Small Batches

There is a hidden feature within sync that does not appear in the user interface.

Companies that may be so large that a full download could error out can actually be sent downstream in smaller chunks, by year.

We have implemented two columns in SSyncDbInfo (2018 2nd Qtr Release version 3.30.0.626) called historyStartYear and historyEndYear that allow you to key in a year value.

When paired with the full download flag on the upstream side (service bureau) the next sync will grab only that year range to sync to the downstream site.

This functionality will only work if both the service bureau side and downstream sync site are at or above this version.

A full download sync will always do a full download of all company and employee tables as per usual, but the tables named below will adhere to the year range entered:

  • EPayEntry
  • EPayHist
  • CJEntries
  • ELaborDist
  • EWorkComp
  • EPayHistDetail
  • EPayEntryDetail
  • EAccrHist
  • CTaxLiability
  • CMiscCheckHist
  • CCalendar
  • CCalendarDetail
warning

There is no UI for this as it is not something that should be used without caution. This functionality is only available via SQL Server directly.

Example​

If you are adding a very large company to RPO, you want to set the historyStartYear to the current year (2018), leave historyEndYear at its default to 2100, then mark that company for full download.

All other companies that exist on RPO would ignore this date as they are not marked for full download. Instead, they just get the data that has changed since the last sync.

Each subsequent sync you can increment the historyStartYear field to get more data in small chunks, so next you would do 2017, and mark historyEndYear as 2017, mark for full download, then sync, then 2016 and so on.

You can of course do more than one year in a range, like historyStartYear = 2015, historyEndYear = 2017, which would download three years worth of history.

note

Each sync when using these new columns will actually replace the prior data if the same year is called again.

warning

Please remember to return the fields to their default values (historyStartYear = 1900, historyEndYear = 2100) once complete, as they do not reset themselves.

Use of these fields is the sole responsibility and risk of each service bureau. It is not in the UI, so we do not support it. We suggest extensive testing to familiarize yourself with the process.

Questions?​

Contact your Payroll Service Provider.