QR: MS-SQL 2014 vs QR 20214.11 - getting past the sys.column_encryption_keys check

[Jon_Donker]

Hi team,

Acknowledgement:

I know that MS-SQL 2014 is not supported and explained to management that our version of QR does not support this database; but they still want me to investigate a work around 🙁 .

Is there an internal parameter for a MS-SQL endpoint to get around the sys.column_encryption_keys check; knowingly that we will be on our own with this method and not expected to receive official support?

0004356: 2026-05-04T09:45:18 [SOURCE_CAPTURE  ]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)
00004356: 2026-05-04T09:45:18 [SOURCE_CAPTURE  ]E:  mssql_ae_is_table_encrypted(...) failed in CREATE STATEMENT for '
select count(*)
from sys.columns c
inner join sys.column_encryption_keys k on c.column_encryption_key_id = k.column_encryption_key_id
inner join  sys.tables t on c.object_id = t.object_id
where c.encryption_type IS NOT NULL and schema_name(t.schema_id) = N'dbo' and t.[name] = N'myTable'
' [1022517]  (sqlserver_log_metadata.c:2343)
00004356: 2026-05-04T09:45:18 [SOURCE_CAPTURE  ]E:  Failed to check if table dbo.myTable has encrypted columns [1022517]  (sqlserver_endpoint_capture.c:158)
00004356: 2026-05-04T09:45:18 [SOURCE_CAPTURE  ]E:  Error executing command [1022517]  (streamcomponent.c:2058)
00004356: 2026-05-04T09:45:18 [TASK_MANAGER    ]E:  Stream component failed at subtask 0, component st_0_SRC_DEV_B1_LAPS_COMLAPS  [1022517]  (subtask.c:1482)
00004356: 2026-05-04T09:45:18 [SOURCE_CAPTURE  ]E:  Stream component 'st_0_SRC_DEV_B1_LAPS_COMLAPS' terminated [1022517]  (subtask.c:1651)

Knowledge base article: https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Errors-Due-to-Unsupported-SQL...

[DesmondWOO]

Hi @Jon_Donker ,

Qlik Replicate will verify the SQL Server version, and R&D cannot provide support for databases that are not included in the official support list. 

Regards,
Desmond

[john_wang · Accepted solution]

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

[Jon_Donker]

Thanks All.

Using a generic ODBC connector isn't a rabbit hole I want to go down.

I have enough to go back to management and say that we cannot connect to 2014 as a source with the version of Qlik Replicate we're running.

[john_wang]

Thanks for the update @Jon_Donker 

At the moment, using the generic ODBC connector is the only available workaround.