The SnapSync job is then suspended and restarted during the next run. For initial loads, the job continues from where it was left off. For subsequent SnapSyncs, the job will start from the beginning. Because SnapSyncs past the initial load are incremental in nature, starting a suspended job from the beginning should not result in full scans of the database if BCT is enabled.