Version 5.2 of SQList is a minor update from ver. 5.0.x, you can therefore upgrade for free if you have a licensed version 5.x. There are no breaking changes in this upgrade.
See below a summary of the changes.
New feature: On demand execution*
* Only available on selected editions
It is now possible to run a SQList synchronisation on demand, rather than as a service that continually checks for changes. This is useful when you do not need to have changes in SharePoint immediately replicated to SQL server, but rather at schedule intervals (e.g. once a day).
SQList can now run as a console application, so it can be executed in a command prompt window, a batch file, or as a schedule job (e.g. using Windows task scheduler).
To run a synchronisation, simply execute SQList as follow:
AxioWorks.SPDBService.exe singleCycle [logToConsole]The parameter
singleCycle instructs SQList to stop running after one synchronisation cycle, rather than keep checking for changes indefinitely. The optional parameter
logToConsole redirect the log messages to the console, rather than the Windows event log (the default).
This is an example of an execution from command prompt:
A few notes:
- The executable
AxioWorks.SPDBService.exe is located in the SQList installation folder, by default: C:\Program Files (x86)\AxioWorks\AxioWorks SQList;
- SQList must be run with administrator privileges;
- If there are errors, SQList will not retry the replication but proceed to the end of the cycle.
New feature: Custom site filter*
* Only available on selected editions
This feature allows you to define an additional filter to the sites exported by SQList. This filter consist of a text file named CustomSiteFilter.txt stored in the C:\ProgramData\AxioWorks\AxioWorks SQList folder, that contains the full URLs of the sites you want to export. This is an example:
Important: Note that this filter is applied after SQList has loaded the sites to export, as defined in SQList Manager, so you still need to define all the sites to export in SQList Manager.
An example scenario where this feature can be used is this: Let's assume you have a SharePoint site with a large number of sub-sites, and you want to control programmatically which ones are exported. In that case you would configure SQList to export all sub-sites, and then you can have an internal procedure that updates the CustomSiteFilter.txt file with the one you want to export. In this case you may have 100s of sub-sites, but only export those that you select in the filter.
Note that the total sub-sites count against the license limits, not those exported via the custom filter.
Minor changes:
- Enhanced change detection: we have made some minor adjustments to the change detection to handle some uncommon scenarios.