Skip to main content
Question

upgrade TX from 20.10.52.64 to 20.10.63.64

  • April 1, 2025
  • 1 reply
  • 18 views

Hi,

our version is 20.10.52.64. Noticed the the Cdata connectors are disappeared for new connections, so want to upgrade to newest version. According to me that is 20.10.63.64 if I'm correct.

 

Are there things to take into account when upgrading to this version? Can I just run the upgrade script from my version to this newest version?

 

Also, is this new version a good version if i eventually want to upgrade to TimeXtender Saas in the future?

 

I've read Download TimeXtender 20.10 – TimeXtender Support, so i know from the "backlog issue”

 

Just want to get confirmed i'm doing the right steps, things, version upgrade :-)

 

thanks!

 

 

 

 

1 reply

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • 1034 replies
  • April 1, 2025

Hi ​@Pieter-Jan 

This version have an improved version of the Migration tool. The benefit of this is that you do not need to create your data sources beforehand as it will use the import export feature we recently implemented in the portal to create them on migration.

So now you just need to create your instances.

You can also do the transfer of one part only, so if you don’t want to transfer the semantic models or the DWH you can choose only to migrate the ODX.

Besides that this version has new Enhanced data sources which can be used instead of most CData providers.

The CData providers you already use can continue to be used in this version as well, so you can do the conversions when you choose to do so. You can also create new ones of the versions you already use.

There was some upgrade issues in version 20.10.58-20.10.61 and all of these issues have been resolved in this one. So this release should give less issues during the upgrade.

When you upgrade and want to be extra certain no issues appear, do an extra backup of all your hosted databases. Once you have upgraded go through each data source and make sure it still is pointing at the correct provider type. Be sure to do this before starting executions or synchronizations.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings