Not supported SQL server version

  • 25 January 2023
  • 8 replies


I’m testing out the new version of TimeXtender. I’ve downloaded the newest version of SQL Server that was suggested in the training material. 

I’ve created ODX and MDW instance, when I try to deploy a table in the MDW instance I get the following error: Not supported in current SQL version



Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64)   Oct  8 2022 05:58:25   Copyright (C) 2022 Microsoft Corporation  Developer Edition (64-bit) on Windows 10 Enterprise 10.0 <X64> (Build 22621: ) (Hypervisor) 


Best answer by harishkm 25 January 2023, 22:39

View original

8 replies

Userlevel 2
Badge +1

Hello @Stefán Gunnar Jóhannsson ,

Thanks for trying out the latest version of TimeXtender.

SQL 2022 is not yet officially supported by TimeXtender. 

You can use any version of SQL up to 2019 for now. 

Userlevel 2
Badge +1

Hi @Stefán Gunnar Jóhannsson,

With the latest release of TimeXtender desktop, support for SQL server 2022 is added.

You can download the latest version from Portal - TimeXtender Training

Please find the release notes below.




I was told that legacy version 20.10.42 was supporting SQL 2022 as well. 

It looks like it is, sort of. I can pick the SQL version when creating stage and data warehouse databases. I’m able to deploy, and create the tables, but execute ends in this error:
Unknown destination server version

Userlevel 6
Badge +5

Hi @Anders sorry for the late response on this. 20.10.42 does indeed support SQL Server 2022. Did you manage to resolve the error? Did you try selecting the deployment target as SQL Server 2022 for you data warehouse?

@Christian Hauggaard ; ended up without choosing a specific deployment target. Adjusted the SSIS-loading a little, and then it works.

Userlevel 6
Badge +5

@Anders thanks for confirming. Could you please let us know which adjustments you made to SSIS loading? 

Can’t remember, but this is how it looks like today:

and no encryption of the connection.

Userlevel 6
Badge +7

Hi @Anders ,


are you actually using SSIS for data movements in this case? If not, I am slightly surprised that you would need to change settings. If you are, what SSIS version did you use before?