Operating systems not listed here are NOT supported. Please contact us, should you have any specific questions regarding software compatibility.
| Server Version | FW v6.0 | v6.1 | v6.2 | v6.3 | v7.0 | v7.1 | v7.2 |
|---|---|---|---|---|---|---|---|
| Windows Server 2019 | N | N | N | N | Y | Y | Y |
| Windows Server 2016 | N | N | N | Y | Y | Y | Y |
| Windows Server 2014 | N | N | N | Y | Y | Y | Y |
| Windows Server 2012 | N | N | Y | Y | Y | Y | Y |
| Windows Server 2008/R2 (64 Bit) | Y | Y | Y | Y | Y* | Y* | N |
| Windows Server 2008 (32 Bit) | Y | Y | Y | Y | Y* | Y* | N |
| Workstation Version | FW v6.0 | v6.1 | v6.2 | v6.3 | v7.0 | v7.1 | v7.2 |
|---|---|---|---|---|---|---|---|
| Windows 10 | N | N | Y** | Y** | Y | Y | Y |
| Windows 8.1 | N | N | Y | Y | Y | Y | N |
| Windows 8 (all versions) | Y | Y | Y | Y | Y | Y | N |
| Windows 7 (64 Bit) | Y | Y | Y | Y | Y | Y | N |
| Windows 7 (32 Bit) | Y | Y | Y | Y | Y | Y | N |
SQL Server versions not listed here are NOT supported. Please contact us, should you have any specific questions regarding software compatibility.
| SQL Server Version | FW v6.0 | v6.1 | v6.2 | v6.3 | v7.0 | v7.1 | v7.2 |
|---|---|---|---|---|---|---|---|
| MSSQL 2019 | N | N | N | N | N | Y | Y |
| MSSQL 2017 | N | N | N | N | Y | Y | Y |
| MSSQL 2016 | N | N | N | N | Y | Y | Y |
| MSSQL 2014 | N | N | N | Y | Y | Y | Y |
| MSSQL 2012 | Y | Y | Y | Y | Y | Y | Y |
| MSSQL 2008 R2 | Y | Y | Y | Y* ^ | Y* ^ | Y* ^ | Y* ^ |
> SQL 2019 is currently unsupported in all versions of Framework, this page will be updated once this compatibility is available.
* Although Windows Server 2008 and SQL Server 2008R2 is supported by the software (subject to the notes/conditions here), it is not recommend that these be implemented into a new environment. Users are encouraged to periodically upgrade their operating system and SQL server versions in line with this compatibility information.
^ MSSQL 2008R2 is compatible for Framework ECM users, only when not running Construction Logistics. Users of Framework Construction Logistics must use MSSQL 2012 or later.
** Incremental security, UAC, and Integrity Level changes being released by Microsoft for Windows 10 may cause compatibility issues in some environments (or for users with certain security/UAC settings). Support for these changes/issues are not supported in older Framework versions.
Note: ODBC SQL Server client-side driver: from Framework v7.2 there is no restriction applied to the version of the SQL client driver that can be used
SQL Server Log Files
1. Log Files are used to track all changes in a database to, amongst other things, provide a point-in-time restore due to a failure.
2. To understand the volume of SQL Log File growth, you investigate what has been changed (and as such logged). Insula cannot assist with the analysis of log files, their growth, etc.
3. In terms of understanding Log Files and their size, growth, and management, Insula recommends implementing the appropriate Recover model for an organisation. Please review the official Microsoft documentation on this. eg. As a starting point - https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-ver15
4. In short, if an organisation's backup strategy is robust and point-in-time restore limitations are understood, a Simple recovery model may be suitable.
5. Where a different (ie. logging) model is used, periodic log shrinking should be done to ensure backups are complete, and logs are shrunk, to conserve disk space. This can be a scheduled/automated process and, again, should be done in accordance with Microsoft's official documentation.