Version 8.4.0.0 of SQList is a minor update; you can therefore upgrade for free if you have a licensed version 8.x. To download the latest version of SQList, visit the Download SQList page.
IMPORTANT, PLEASE READ: although we always strive to make upgrades as hassle-free as possible, we strongly recommend that you follow the installation and upgrade steps described in our support article:
How do I install or upgrade AxioWorks SQList?
Replicate Required/Optional columns as NULL/NOT NULL
A new setting has been introduced to export the required SharePoint column as NOT NULL in the corresponding SQL table. This means that SQL columns will be set as NOT NULL if the relevant SharePoint column is marked as “Required.”
Please note that if this setting is enabled for an existing SQL table that already contains NULL values in that column, SQList will generate errors, as it cannot alter the column from NULL to NOT NULL (which is the default setting). Before enabling this option, it is essential to ensure that all values in the SQL table are not null.
Additionally, be aware that SharePoint is relatively relaxed in enforcing rules; while empty values will not be allowed through the UI, they can still be easily inserted via APIs or lower level code access. Therefore, use this option with caution.
Diagnostic Report
We have added a Diagnostic Report that conducts a thorough health check of the SQList installation and replication configurations. This is a more advanced version than the existing error report. The report is essential for investigating issues with replication and provides crucial information and warnings that will enable us to address issues more accurately. The report can be emailed directly from the UI for our analysis.
Auto-Repair feature
In addition to the Diagnostic Report, we have included a Self-Repair feature that automatically detects and fixes issues with the SQList installation.
IMPORTANT: This option should be used with caution; we recommend it is only utilised following our instructions.
Fixed minor bugs
We have resolved minor bugs, including an issue where the instance table was created in databases not configured for replication. This bug did not impact the replications and was more of an annoyance than anything significant.