Qlik Replicate: Errors Due to Unsupported SQL Server Versions

[john_wang]

Starting from Qlik Replicate versions 2024.5 and 2024.11, Microsoft SQL Server 2012 and 2014 are no longer supported. Supported SQL Server versions include 2016, 2017, 2019, and 2022. For up-to-date information, see Support Source Endpoints for your respective version.

Attempting to connect to unsupported versions, both on-premise and cloud, can result in various errors.

Examples of reported Errors:

• Qlik Replicate 2024.5 accessing Microsoft Azure SQL Server 2014
  
  [SOURCE_CAPTURE  ]W:  Table 'dbo'.'tableName' has encrypted column(s), but the 'Capture data from Always Encrypted database' option is disabled. The table will be suspended  (sqlserver_endpoint_capture.c:157)
  
  
• Qlik Replicate 2024.11 accessing Microsoft SQL Server 2014
  
  [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: 42S02 NativeError: 208 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Invalid object name 'sys.column_encryption_keys'. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:4067)

Cause

The system view sys.column_encryption_keys is only available starting from SQL Server 2016. Attempting to query this view on earlier versions results in errors.

Reference: sys.column_encryption_keys (Microsoft Docs)

Resolution

Upgrade your SQL Server instances to a supported version (2016 or later) to ensure compatibility with Qlik Replicate 2024.5 and above.

Internal Investigation ID(s)

00375940, 00376089

Environment

• Qlik Replicate versions 2024.5, 2024.11, and higher
• Microsoft SQL Server 2014, 2012, and lower (unsupported)

[HOASTONGE]

It's not normal to Upgrade SQL Server database source where we don't have full permission on it ..
How can I disable that

Upgrade your SQL Server instances to a supported version (2016 or later) to ensure compatibility with Qlik Replicate 2024.5 and above.

[HOASTONGE]

How can I backforward my installation of Qlik Replicate ... all job are trouble since I installed the last version .. I tought I must be refresh my env.. but it not the case .. I step forward .. 

[Dana_Baldwin]

Hi @HOASTONGE 

Please refer to the PDF at this link for how to back out a Replicate upgrade: Qlik Replicate Upgrade Best Practices - Qlik Community - 1729651

I apologize for the trouble you are having but unfortunately using a version of an endpoint or driver that was not certified with the version of Qlik Replicate that you are using can lead to unpredictable results. We can investigate if you want to open a support case, but it is very unlikely that we will be able to issue a patch for an unsupported configuration (if there is a software defect involved).

[john_wang]

Hello @Jon_Donker ,

Qlik Replicate validates the SQL Server version during both the Full Load and Change Processing phases. This is why the same error occurs even when running a Full Load–only task.

As a workaround, you can configure a 64-bit ODBC DSN and use a generic ODBC source endpoint to connect through that DSN. This approach can be used for a Full Load–only task or Using ODBC with CDC as a source.

Hope this helps.
John