A console application called LssApplyDeltas.exe is able to apply deltas to an existing LSS store, called a "level 0", to bring it more up to date.
On the command line two or three arguments may be specified...
LssApplyDeltas level0path deltasDirPath [cpsn2]
Argument 1 level0path The path to an existing LSS store, called the "level 0" Argument 2 deltasDirPath the path to the directory containing the delta-files Argument 3 [optional] cpsn2 A "one past end" value of the cpsn, to specify what delta files should be applied to the level 0. The half open interval [cpsn1, cpcn2) is applied. cpsn1 is determined automatically from the level 0 file. Note that delta files are applied up but not including cpsn2.
LssApplyDeltas can be passed the cpsn2 parameter to limit the number of deltas to be applied. Currently this is only at the course granularity of check-point boundaries. [In the future it is expected that it will also be possible to specify a date/time stamp for more precisely controlling what transactions are applied]
If the delta files directory contains the delta files from 0 onwards, and there is no level 0 LSS file, then LssApplyDeltas.exe will actually create a level 0 from the delta files
The LSS always uses the extension "partial" for the current delta file being written. This is renamed with the extension "lssdelta" after the delta file has been completed. It is assumed that this approach is sufficient to ensure that LssApplyDeltas won't apply a partially written delta file.
LssApplyDeltas is idiot proof in that it will never apply an inappropriate delta.