Skip to main content
IMPLEMENTED

Allow Data Movement from Prepare to Prepare

Related products:TimeXtender Data Integration
  • March 19, 2025
  • 3 replies
  • 52 views

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8

In TimeXtender Classic you can have as many Datawarehouses as you want and move data between them. While you can add many Data Areas inside one instance in TDI, you cannot have data move from one Prepare Instance to another.

The main advantage to this is that each Prepare Instance can be its own, appropriately scaled, infrastructural entity. One example is the situation where you have an implementation that starts growing horizontally: adding more subcompanies to a group, or adding more data due to acquisitions. In this case your database might not be scalable to handle the new data, or the project might be getting too large.

 In this case instead of scaling up a huge database to be able to handle the peak load, you can split out into smaller chunks. This also allows separating out HR data into separate hardware.

3 replies

andrew.gebhard
TimeXtender Xpert
Forum|alt.badge.img+4

Hi team,

This is an important issue and introducing this flexibility would allow for better governance of data.

For example, a prepare instance creating a ‘silver’ tier data product could have different devs and be the source for a prepare instance creating a ‘gold’ tier data product. 

For blueprint instances, this is also pretty much a necessary feature. Clients want to use a prepared prepare instance to gather a certain type of data, but would almost always like to combine this with other data that they gather about their organization. 

Kind regards,

Andrew


Thomas Hjermitslev
Community Manager

We’ve implemented selecting and transferring data between Prepare instances in TimeXtender Data Integration 7256.1.

 

Currently, it is only supported with SQL Server storage, so I won’t tip this idea to “implemented” just yet.


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • February 3, 2026
SUBMITTEDIMPLEMENTED