To homepage To homepage
Solved

TX Upgrade from 20.10.45 to version 6521.1

  • 26 February 2024
  • 4 replies
  • 114 views
avanrijn
Rank
Badge

Dear Sir,

I am assisting one of our clients with a TimeXtender upgrade from 20.10.45 to version 6521.1.

I gave them a small demo today and showed them the Migration Tool to support the upgrade proces.

Then the client asked me if the Migration Tool is capable to Migrate over a 100 TX-projects all at the same time…. Yes, you are reading this correctly, our client has over a 100 TimeXtender projects.

So, I am looking for a way to Administrate all of these projects in the Environments Page (see picture) and please advice how to speed up the TX Upgrade proces for our client. If we can’t automate the migration-proces it’s going to be a lot of work.
 

I hope you can shine a light on this one, because I am still in the dark.

Thanx in advance.

Regards from Amsterdam,

Arthur
 

icon

Best answer by Thomas Lind 16 April 2024, 09:14

View original

4 replies

rory.smith
Rank
Userlevel 5
Badge +7

Hi @avanrijn ,

the new release does not have a project as an entity: your environments are shared across all instances that are part of the TX deployment. If the things your projects are doing are separate (and need to stay that way) they will occupy separate instances inside the environments specified. I.e. there might be one ODX, but 100 DWH instances * the number of OTAP/DTAP phasings you have.

It is probably a good idea to reach out to your Solution Specialist given the scale :-)

Thomas Lind
Rank
Userlevel 6
Badge +5

Hi @avanrijn 

When you migrate from LTS to SaaS, it will be the project you have open when you press the migrate button that will be migrated. A project can’t share BU and DWH databases with other projects, but it can share an ODX.

I agree with Rory, it will be 100 unique DWH instances if you have that many projects and possibly as many or even more SSL Instances, so I don’t see an easy process for this.

Thomas Lind
Rank
Userlevel 6
Badge +5

Hi @avanrijn 

I did some research on this. I was a bit wrong about the limit. There is no limit to how many projects you transfer to one DW instance. The data areas can have the same names as well, it will just add the project name to the data area name on the other end.

To show this I tried to migrate three different projects to the same DWH instance. The only issue was that I needed to generate the data sources beforehand, but other than that it worked fine.

So this means that you can transfer 100 projects to one instance as long as you have the data sources set up in a ODX instance.

avanrijn
Rank
Badge

Thank you Thomas for looking into this.

Regards,

Arthur

Reply


Terms and ConditionsCookie settings