Table '%1' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision,
defeating download filtering
Probable cause
A remote database is synchronizing a table with at least one timestamp column while the timestamp precision on the remote
database is higher than that of the consolidated database. The uploaded value will lose precision after being stored in the
consolidated database. The MobiLink server compares upload rows and download rows in order to filter away redundant download
rows. The loss of precision may create a virtual difference that defeats the download filtering. This situation can affect
download performance. To avoid this performance penalty, you should align timestamp precision across all databases involved
in your synchronization system.