Permissible MSSQL Versions per Dalet Version and Revision

This article highlights the permissible MSSQL versions for Dalet versions (Radio Suite, Enterprise Edition, and Galaxy) and their revisions.

Dalet Policy for Microsoft Product Compatibility

Dalet does not have the capacity to handle Microsoft testing on top of Dalet products and the various third party integrations we commercially support.

We test for *compatibility* (vs. "support") of Dalet products against Microsoft OS as a by-product of  their daily use in the R&D, as early as these are stable.

Our policy for compatibility validation of Microsoft products (OS, OS updates, SQL) is that Compatibility tests are performed as a 'by-product' of normal daily work:

• Automated test platforms (daily deployment of trunk/SP, configuration and end-to-end regression testing)
• QA platforms, with a mix of workstation and server OS versions (daily deployment of trunk/SP/MF, feature testing, end-to-end system tests, nonfunctional tests)
• New OS and SQL versions are installed as they are released on the above mentioned platforms (after SQL validated by our in-house experts from the alpha stage)
• Automatic pushing of Critical and Security type updates to all hosts in the DALET domain
• Periodical (usually bi-monthly) push of all Microsoft updates, including Windows 10 major SPs
• Achieve compatibility by fixing bugs or developing features as required
• Maintain documentation in the Dalet Wiki (for OS and SQL)

SQL Validation Policy

Dalet Galaxy Service Packs and Hot Fixes (MFs) versions are validated against the latest MSSQL release only.

See Microsoft MSSQL Lifecycle table.

Checking SQL version

In order to find out the MSSQL version, use the following query:

select @@version

SQL Compatability Level

When Microsoft brings out a new version of SQL Server, the newest features are only available in the newest compatibility levels. Every SQL server version has its own compatability level. For example MSSQL 2022 has a compatability level of 160, SQL 2014 has one of 120. 

On upgrading MSSQL, make sure that the compatibility level of the restored database is changed to that of the upgraded MSSQL version. For example, if you are upgrading from SQL Server 2014 (12.x) to SQL Server 2022 (16.x), you should also update the compatibility level from 120 to 160.
Failing to do so may lead to compatibility issues and prevent optimal performance.

Best Practice on Upgrading SQL

• SQL Server Memory properly configured
• Compatibility Level Updated
• Query Store is Enabled
• Max Degree of Parallelism (and Cost Threshold of Parallelism) is properly configured.
• Lock Pages in Memory configured (Especially if running on a VM)
• Instant File Initialization configured
• TempDB configured properly (8 files).
• Dalet Galaxy: check pr_CheckSQLCompliance / pr_CheckSQLComplianceWarnings / pr_CreateCheckSQlComplianceWarningsJob before upgrading to the latest MSSQL SP to make sure it is compatible with your project version.

Dalet Galaxy five, Dalet Galaxy, Dalet 3.x, Dalet RadioSuite HD

Versions (see detailed table below): MSSQL 2022, MSSQL 2019, MSSQL 2014, MSSQL 2012, MSSQL 2008.

Compatible Versions

Ongoing Dalet Galaxy Service Packs and Hot Fixes (MFs) versions are validated against the latest MSSQL release only.

It is highly recommended to use MSSQL 2019 and above with Dalet Galaxy five 4.0.383 for improved performance.

* For SQL 2012 Latest SP Check Dalet's pr_CheckSQLCompliance / pr_CheckSQLComplianceWarnings / pr_CreateCheckSQlComplianceWarningsJob before upgrading to the latest MSSQL SP compatible with your project version.

Starting from SQL 2017, no SQL Service Packs are released, only Cumulative Updates are available. SQL Server CUs are certified to the same levels as Service Packs, and should be installed with the same level of confidence

SQL 2017 and above: Quarterly basis and pick the latest CU available

SQL 2016 and below: Latest validated SP. Consult a Dalet representative

Important Information on the ODBC SQL Driver Version & 64bit Dalet Galaxy

Use the SQL Server Native Client 11.0 only to connect to SQL. Use the 64 bit version which you can download from the Microsoft site:
https://go.microsoft.com/fwlink/?LinkID=239648&clcid=0x409.
There are various revisions of the above mention  Native client 11 (2011.110.2100.60).

Do NOT download just any, but only the one linked above. Otherwise you may encounter serious DB_Server issues, such as the inability to create titles etc.

Concerning Dalet Galaxy five, versions 352 and 383
a new version of SQL Server Native Client is validated, 18.1.1.1.
https://go.microsoft.com/fwlink/?linkid=2202930
when moving from an old version to this new one, e.g. from 2011.110.2100.60 to 2018.181.01.01
you could face this error:

In that case you use Encryption=Optional instead of Mandatory.

Additional Dalet Products

Dalet Brio

MSSQL Express Edition 2022; basically every Express edition from MSSQL 2005 and above. Some Brio apps, such as Media Navigator use the express edition (for it is free). Dalet QA uses MSSQL 2019 Standard Edition internally.

Dalet Cube

MSSQL 2012, MSSQL 2014, MSSQL 2016 (including SQL Express).

Dalet CubeNG

MSSQL 2017 (including SQL Express).

Dalet Amberfin

Dalet Amberfin will use an MSSQL database only if so configured specifically, otherwise it is using its private H2 db.

MSSQL 2012, MSSQL 2014, MSSQL 2019, MSSQL 2022 have been validated.

Dalet SportsFactory / SportsLogger

MSSQL 2005 to MSSQL 2016 (latest SP).

Dalet Report Center (DRC)

MSSQL 2012 to MSSQL 2016.

Related Articles

Operating Systems Compatibility for Dalet Products

System Recommendations For Dalet Products

Recommendations for Dalet Enterprise Edition 3.5

Recommendations for Dalet Radio Suite HD and Dalet Galaxy Radio