Recently active topics

Hello,TimeXtender 20.10.31.64ODX: 20.10.31We are currently running a database on hyperscale with 12vcores and premium memory optimized hardware. ODX is a data lake.We are running execution packages on 4 threads and we want to reduce our odx transfer times as that is out biggest impact right now.This is an example of a load. I am seeing long ODX transfer times for very small tables that I cant find the cause of or explain.We have alot of small tables (see example below) that is taking 1-3 minutes, while some tables doing data cleansing on 1million + rows is doing it in the same amount of time. See this small table that is 400 rows, no transformations and only 10 columns. I can see we are peaking log io at 100% during certain periods.However, that seems to be during the later parts of the loads and not during odx transfer in the start. Is there any thing that can cause this or possibility to improve it?Thank you,Victor​​​​​

Hi, I’m running TimeXtender Data Integration 7158.1.When integrating an existing object I accidentally got a few extra tables, or MDW schemas, into my project that I didn’t intend to integrate.Now I’m having a hard time removing them from the project. Going through the ‘integrate existing objects’ window without having those schemas selected does not help. In two cases could drop the tables and remove them that way but I don’t want to remove txdsa.ODX_TEMP tables (while running). I thought of simply reverting my version but as of now it seems that the open folder is disabled. I do see version notes though but no way to revert to that version.Any ideas? 

Er det muligt fra en version 20.10.xx at foretage migration til fabric uden at skulle gendanne alle objekter ?

Hi Everyone, In the Ingest instance activity log I see a lot of messages. It happens when populating a table in the DSA (execute). We are using Datalake as storage and TDI version 7158.1Execution takes a loooooong time also. What goes wrong here???  

I have the following problem when I perform the migration between environmentsIn Ingest instancesAfter migrating, I have to remap the metadata, select all the tables again.En Prepare instancesThe mapping table bring the source of developer environment and not  prod And Can I create two data source with the same short name?  

I configured a REST API endpoint. It woks as expected as long as I only add tables from my MDW to the endpoint. However, any views I add to the instance in TX are not visible through the API. They do not show up in the /swagger nor can I query data from them nor can I find any mention of then in the webserver configuration. Why is that?

Hi team, I want to create a new enviroment variable that I used to do in the old version, but with new version it changed. The idea that create a new enviroment varible, and configure on execute package, the variable check dev enviroment or prod enviroment and if it prod the execute package will run. My Version isHow can I do that?

Hello,I use TimeXtender CSV Data Source (version 23.18.5.0). I'm trying to read about 15 csv's from an sftp server, but since january 15th 2026 we get an error. This server is hosted by an external supplier which has it's settings limited to max 1 session (no concurrent sessions).In TDI I've configured the max concurrent threads on 1, so max 1 thread at a time. My transfer still crashes because I use too many threads.I tried to put max concurrent threads on 0. This resulted in a never ending transfer task. Didn't work.After this the supplier increased it's max threads temporarily for testing purposes. I configured the connector on 1 thread again. If I look in the log, I can see that the first 2 tables start on the same timestamp. This occurs a couple of times more. Is the connector using 2 threads now?Is this advanced max thread setting working correctly for the TX csv connector? Supplier claims we're not using 1 thread. I'm not sure how I can check and prove this. Do you have any advi

When I try pagination in the Enhanced datasource REST I only get 1 run, it stops after the first page.My Json result looks like this when I get to a page without a result:{    "data": [],    "status": "success"} How do I get my stopCondition to work in pagination?

CData is imposing a monthly fee on customers that use their connectors after 5 March 2026.It’s easy to switch to TimeXtender connectors but it can be a tedious process in larger solutions with many projects to find those connectors.Here’s a query you can run against the project repository to get a list of currently used connectors:/***** Current CData Usage *****/select p.Name as Project      ,s.Name as DataSource      ,left(stuff(c.ProviderName, 1, 18, ''), charindex('.', stuff(c.ProviderName, 1, 18, '')) - 1) as Provider  from CDataDataSources c  inner join DataSources s on c.CDataDataSourceId = s.DataSourceId and s.ValidTo = 99999999  inner join BusinessUnits b on s.BusinessUnitId = b.BusinessUnitId and b.ValidTo = 99999999  inner join Projects p on b.ProjectId = p.ProjectId and p.ValidTo = 99999999  where c.ValidTo = 99999999  order by 1, 2

I have been trying to sort out something out,My JSON looks like this:addendumGroupName occurs multiple times. Here, its 4 times but in other cases it occurs between 1 to 50.columns can be one or multiple I am trying to list all addendumGroupName and all columns under each addendumGroupName without doing this:json/addendumValues/addendumGroups[2]/addendumGroupName[0]json/addendumValues/addendumGroups[2]/rows[0]/columns/fremdrift_group[0] json/addendumValues/addendumGroups[2]/rows[1]/columns/fremdrift_group[0]json/addendumValues/addendumGroups[2]/rows[2]/columns/fremdrift_group[0]  So i tried this (with an without [*] at the end of column name): <attr name="addendumGroupName" xs:type="string" readonly="false" other:xPath="/json/addendumValues/addendumGroups[*]/addendumGroupName[*]" /> <attr name="fremdrift_group" xs:type="string" readonly="false" other:xPath="/json/addendumValues/addendumGroups[*]/rows[*]/columns/fremdrift_group[*]and for JSONpath:<api:set attr="detai

Designating a field as “raw-only” allows for the field to be hidden from the valid version of the table but still available for use as the basis for other fields, which can help streamline the valid version of the table. As the name implies, a raw-only field is a field that only exists in the raw version of the table and not the valid one.Raw-only fields will not be displayed in other Data Areas or Deliver instances that only use the valid part of the table. Hiding a field from the valid version of a table can be appropriate for fields that have no other purpose than to be part of other fields, e.g., used to create a surrogate key for dimensional modeling.Use the following steps to designate a field as raw-only:Right click the field and click Raw-only field. Raw-only fields are displayed with an “R” in their icon. Raw-only fields cannot be added when dragging fields from one data area to another. Raw-only fields also cannot be added when attempting to drag fields to a Deliver instan

In March 2025, we announced plans to deprecate CData providers to streamline our platform and focus on TimeXtender Enhanced connectors. While we believe our native connectors offer the best long-term performance, we understand that flexibility is key to your success and that many of you requested more time or options.We are pleased to share that CData providers will remain available and supported, giving you continued flexibility and choice. CData connectivity will be offered as a premium option, allowing you to remain on CData if you need additional time or prefer the existing functionality, without disruption to your operations.The detailsPricing: 250 USD / 250 EUR / 250 GBP per month per customer account (billed in your subscription currency). Usage: This fee covers unlimited use of any CData providers you need for that account. Effective date: Billing for this service will begin on March 5, 2026.How it worksWe have designed this to be seamless. You do not need to sign a new contrac

We have recently updated a TimeXtender version from 20.1047 to 20.10.74 and was successful for Development and QA but after updating Production the SSIS Packages are not executing. Development and QA have the same version of SQL as Production. The execution of SSIS Packages is setup through External tasks. The only relevant information I have found so far regarding this issue is here (https://legacysupport.timextender.com/hc/en-us/articles/360000169786-Troubleshooting-Upgrade-Issues) but am not sure how the steps under heading ‘Cannot deploy or execute SSIS packages’ would resolve the issue. Anyone else run into this?

Hello,Since the TimeXtender Classic (V25) was announced to be released by the end of Q2 2025, i would like to ask if there is a clarified date when the release is planned. To my knowledge it has not been released as of yet? Also the more important question to me is the upgrade process. Currently we are using TimeXtender classic together with ODX server and we have couple of questions:Will there be a detailed guide released on upgrading older TimeXtender platforms (20.10.52 in our case) to Classic V25? What will happen with all the data sources in our ODX instance? Since we are using quite some CDATA providers - does it mean we will have to manually recreate the data sources? Or ODX will be deprecated and we need to move to using BusinessUnits? Thanks for the information

Hello, We have a project that is on 20.10 (will upgrade to classic when it is released later this quarter).The customer has a source that is apache iceberg that we want to get data from but I can’t find any information regarding that for TimeXtender. Has anyone done this yet in TimeXtender, if it is even possible to ingest it?Thank you

Does anyone know if there’s a way to export all open and closed tickets for an organization? If not, is it possible to easily set up an automated Python process (e.g., by doing web scraping) to save them to an Excel spreadsheet?

 At TimeXtender, we provide robust and flexible options for deploying our Orchestration & Data Quality (O&DQ) solutions. These deployment options ensure that you can integrate and maintain the highest data quality and consistency across your systems, regardless of your organizational infrastructure and technical constraints. In this article, we will explore the various deployment options for TimeXtender's O&DQ offerings.Deployment OptionsTimeXtender's O&DQ solutions can be deployed in a variety of environments to meet the diverse needs of our customers. These options include:Cloud Deployment On-Premises DeploymentCloud DeploymentCloud deployment is an ideal choice for organizations looking to leverage the scalability and flexibility offered by cloud platforms. This is the default setup for customers and here TimeXtender hosts the repository database, execution engine and web interface, while end-users connect to the environment using a browser and desktop client.Connect

 Triggering a Fabric Data Pipeline from TimeXtender Orchestration Integrating Fabric Data Pipelines with TimeXtender Orchestration allows you to automate your data workflows and ensure seamless operation. This guide provides step-by-step instructions on how to trigger a Fabric Data Pipeline using PowerShell and wait for it to finish successfully.Steps:Add the App Registration into Global Parameters Create a Query Snippet using the provided code Create a PowerShell package that defines the pipeline id and references the Query Snippet1. Add App Registration into Global ParametersTo enable secure communication between TimeXtender and the Fabric Data Pipeline, you need to add your App Registration details into the Global Parameters. Follow these steps:Navigate to General > Configuration in the TimeXtender Orchestration module. Open Global Parameters and click Add. Add the following parameters:AppReg_TenantId: Your Tenant ID AppReg_ClientId: Your Client ID AppReg_Secret: Your Client Secr

Is there Swagger import support for the new TimeXtender REST data source?

I have a source table in ODX. The source only keeps record for the last 3 months. UUID ColumnA ColumnB ColumnC Date 1234 Xiaomi Mobile phone 125 GB 01.01.2025 5678 Apple iPad 1 TB 01.02.2025 9101 Samsung Mobile phone 256 GB 01.03.2025  When i am in month 4, the forst row is unavailable in the sourceUUID ColumnA ColumnB ColumnC Date 5678 Apple iPad 1 TB 01.02.2025 9101 Samsung Mobile phone 256 GB 01.03.2025 11121 Google Pixel Mobile phone 256 GB 01.04.2025  I want to keep the history in DSA forever.I know that if i create a history table and use UUID as unique key, i will be able to keep the history.The question is: what if i accedently execute the table on 01.04.2025! Will i lose everything before 01.02.2025? Or will executing the table keep the history intact !What if there are changes in the source and there is either a new column or the column name changes? I need to then deply the table. Will that keep th