Build better products with our product team
Currently the execution log of an Ingest Transfer task is limited. Extracting in TimeXtender Classic with business units has for instance, the advantage of a gantt chart so one can see which tables take a long time to load.We have a transfer task that extracts 200+ tables, some of them are incremental. Currently the execution takes about 2 hours, but it is very hard to investigate which tables in particular consume the most time.It would be nice to have a more detailed log for Ingest instances, so you can see the execution time per table.
If we have a job scheduled with a ODX transfer task it’s not possible to get a notification email if the job finished with errors.I think that it’s necessary.
In ODX Server v20 there is the option to restart a Transfer if failed, similar like the mechanism on Execution Packages. In TX/ODX Server v21 the scheduling of Transfers is handled by Jobs, but the option to restart a task if it fails is missing: Especially some of our REST API data sources return an error. The retry/restart option is crucial here.
Hi,Would it be possible to remove the release number from the names of the Timxtender Windows services.It would it would help if the name to remain the same when using monitoring systems. For example OP5.The release number can still be in the description.There is no reason to have more than the latest version installed, right? Because you can still only run one version of each service on one server. And once you've upgraded, you can't go back.So existing services would be replaced with the new version during installation.BRAnders
In version 20.XX and previous, double clicking tables in the data lineage visualization made you jump to them in the GUI. It would be great to have this function added in verson 6XXX as well.It is both a useful tool for the developer, as well as an impressive feature to show in demos.To trace lineage in the current version (6284.1) you would manually have to find the table shown in the data lineage view, which in larger DW instances can be difficult.
I have 3 DWH instances that all contain the same table. If I generate lineage from the ODX, I cannot see which is which: It would be good to show the instance name and be able to filter by them.
When you run through lineage for data that involves a table insert or related table insert, clicking those does not highlight the object in the GUI. It only makes the connected tables bold in the lineage view. If you double click a default view or parameterised custom view, this does work.
Hi,Wouldn't it be nice if we are able to go directly from the impact analysis or data lineage overwiew to the table or field you would like to zoom in/ or change? Actually the same as the "go to source field” option on a Copy From field but then within the data lineage overview.Kind regards,Devin
In the previous set-up (v 20.10.32.64 for example), it was possible to simply click-through from the lineage view to one of the objects on the line. A feature I found extremely handy.It seems to me that this functionality no longer exists in the all new TimeXtender.Will you be adding this feature again soon?Kind regards,Dirk Meert
When using aggregate tables in version V6XXX, it is showing only the bottom up approach is not showing the source table of the aggregate table and the data source.This worked correctly in versions V20.10.x.
In the Bar graph we can see only the task when it’s finish:It will be very usefull to see a bar for the task when it’s running (In green color for example)
Add a functionality for the user to define custom key shortcuts for menu items. As some actions are done very frequently (e.g. previewing a table), it would be nice to make them a bit easier.
When you add a list of tables in the execution queue and a reload is failed, you can see the error message. But you must manually scroll/find the table to fix the error.It would be great if there is an option to go to the source table from the execution queue window.
When dragging a table from the Ingest instance to the Prepare instance it would be extremely useful if TDI could check if the table is included in a transfer task. If not then it would generate a pop-up window asking if the user would like to create new transfer task and/or add the table to an existing transfer task.
Power BI and SSAS Tabular allow you to use a setting to apply Row Level Security on relationships that are bi-directional, or filter both tables. This feature is needed in TimeXtender's semantic layer.
Dear all,What would greatly improve the connectors in the ODX is a connector which would look at a folder / container and copy all the files in the container / file location to the Data Lake in (Delta) parquet format.My client has a lot of different data files (csv / excel / flat files) which land dat different moment in time which all ‘just’ need to be transferred to the TX eviroment (read: converted into parquet / delta / SQL table) and then they should be selectable from the ODX to be transferred to the DSA.I know that in ADF these kinds of loops can be made, but It would be great if TX offers such a connector.
I suggest something like this:If it’s selected it will do a Full Load in all the tables, including the incremental tables.Now it’s crazy to do that if we want fully load only one table.
Dear all,I've always found it a great feature in TimeXtender Classic to be able to export your project and then import it again.What I think would be a great feature is to be able to have a instance, let say you've created a Prepare instance on ‘Exact Online', and TDI lets you import and merge the Exact Online instance with your current Prepare instance.This would open up a lot of possibilities with enabling new clients with instances that you've already created. This would also open up the possibility of ‘sharing’ templates of certain standard sources so you don't have to build everything from scratch.
As you can see in the image we can have many External Executables. It would be nice to be able organizate it in folders.
Sometimes, you can experience wrong/strange sortings of your textual data in the semantic model. This is caused by the collation of the Power BI Premium endpoint not being set to what you would usually do in your geography had it been a regular tabular analysis services endpoint. According to this: https://data-goblins.com/power-bi/case-specific it should be possible to change the collation – although not through the standard interfaces, but only through Tabular Editor or directly editing the file. I would like to see TimeXtender added to that list.
When running TimeXtender in a scenario with ADF-enabled Ingest server you will find that a single pipeline with merge transfer is used on execution. Handling in the DSA etc. will only start when this merge transfer is fully complete. This means executions in the new release are less performant than they could be. Perhaps there is one table that takes 2 hours to copy blocking execution on a very powerful SQL instance hosting the Prepare instance where the faster tables have expensive cleansing that could be run in the meantime.The idea is to allow a number of pipelines to be defined, where TimeXtender can allocate transfers across them similar to how this is done in threading. This way Prepare instance execution of tables allocated to a 'faster’ pipeline can proceed while some of the longer Ingest instance → Prepare instance data movements are still being handled by a 'slower’ pipeline.Execution management should then take transfer and cleanse times into account to make a smart decision on allocating tables to different merge pipelines with the goal of reaching the shortest overal execution time possible.
Hi team, When executing multiple tables in a data area that are using ADF for Ingest instance → data-area transfers, one ‘Ingest Merge Transfer’ task is often created. This is not represented in the Gantt chart:In practice this means that the logs for many of my execution packages are filled with predominantly white space. This also does not allow me to see any threading that might take place to allow more efficient data processing, but judging by the white space and the behavior of the cleansing tasks, I do not believe threading is taking place. I would like to see more representation (any representation) of these transfer tasks in the gantt chart and execution logging. Kind regards,Andrew - E-mergo
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.