TimeXtender Desktop Q&A

Hi team, I need to audit how many rows were moved by batch on the prepare table. Is there in TX how to audit it?ThanksCarlos

Hi Team, Hope you are well!!We have received CVE-2024-21907 Kenna Vulnerability in SUN ODX Servers to upgrade SSIS from version 15.0.4440.1 to version 15.0.4455.2. Could you please confirm whether we can update this to the latest version? The SSIS package used for integration, I am not really sure if this will affect the existing integration.?

Hi,Is there some documentation available for the metadata in the exmon database, on how the DB model works? We would like to create some useful queries for troubleshooting purposes, to find problems in the run.(I found this old thread where the last post asked the same question: Exmon run stats into PowerBI | Community. Don't know if it was answered somewhere else) Thanks! Willem

Hi, We've setup a REST API web server according to the manual. On the resulting endpoints fieldnames always seem to start lowercase. The original fieldnames in the deliver instance start with a uppercase letter. Now, I know that there should be a way to edit this in the configuration of the web server.Is this something we can edit ourselves? I've tried looking up directions, but web servers are not my expertise and I am unsure if the source code for the web servers is available locally or only in the cloud repository? Vilsen, Luuk Bouman

I am having some issues with the transfer step when loading incremental using direct read. The problem seems to be that the generated procedures do not utilize indices on the underlying tables, resulting in full PK scans for every run.I was especially having problems when running on azure general compute. Switching to hyperscale helped some, but the transfer step still uses approx 40sec scanning ~90m rows causing bottlenecks. When using ADO.NET I could set an index on the incremental rule-field speeding up the search to <1sec.The execution-plan generated by TX looks like this: Here we get a PK index-scan even when there is an index on dw-timestamp.Testing on a subset of the data (~10mill rows): Adding the option(recompile) to the procedure results in the procedure using the dw-timestamp index: Is there a good reason for why these procedures are generated without the recompile flag?Is it something that could be added in a later release?And is there a way to work around this other tha

I have 3 big fact tables in the source which i load incrementally. Primary keys are CompanyID and EntryNo (applicable for each table separately, incrementing), the records in these fact tables are never deleted.I need to merge these tables to a single table in DSA layer also incrementally. I think of following setup:Make the DSA table also incremental, check “Don’t handle deletes” (as the records are never deleted in source) Include both CompanyID and EntryNo as primary keys in the table; Incremental Selection Rule → EntryNo > (Last max value); Map all tables from source in this single DSA table The result which i expect is every time DSA table is executed - it incrementally loads data from 3 related fact tables - based on EntryNo for each separate CompanyID (one CompanyID per one source table). This way i have one huge table containing all the records for all 3 “Companies”. Am i correct to assume this is the setup i need? Are there any risks with possibly missing or overwriting the

Hello,What’s currently the recommended alternative for the CData Googlesheets provider when we switch to TimeXtender Enhanced providers?Kind Regards,Hendrik

Hi teamI have created this Schedule Groups,  The ingestion process packages are working fine, but the prepared packages are not working. the message log is:Logfile output: 5:01:53 AM UTC now: 2/20/2026 5:01:53 AM5:01:53 AM TimeXtender Version 25.2.0.57 built 11/10/2025 2:15:00 PM. Running on vm-orc-prod-0075:01:56 AM PID: 42376  - Started with arguments: --startschedulegroup 9 --execute_uat PROD --schedule_group 9 --customerkey uim --use-saas-queue true --token ece94e91-e0af-4588-9844-80e5e7f952cd --is-saas-local true 5:01:56 AM Connected at 2/20/2026 5:01:56 AM5:01:56 AM 5:01:56 AM *** Executing schedule group 165:01:56 AM Running schedule group CortexPolicy on PROD with 4 tasks.5:01:57 AM 2/20/2026 5:01:57 AM Starting: GWPCProd Load Data (Incremental Load) (CortexIngestServiceDLSProd) - (28) Extra Param: 5:01:57 AM (28) Command : epcmd --uat PROD --startpkg 28 --parentexecid 31 --use-saas-queue true --execute_uat PROD --token ece94e91-e0af-4588-9844-80e5e7f952cd --is-saas-local true

Hello,I am connecting to an external blob storage using a private endpoint. The blob storage is structured as follows:parquet/ 2025-12-29/ Acquisition.parquet Asset.parquet AssetBalanceSheet.parquet … User.parquet ValuationAssumption.parquet 2025-12-30/ Acquisition.parquet Asset.parquet … Etc. I am using the TimeXtender Parquet Data Source provider. The connection works, but the results I get from the Metadata Manager are not what I expect.Current settings Path: parquet/ Include subfolders: Yes Included file types: parquet File aggregation pattern: Asset.parquet Expected behaviorI expect the Metadata Manager to return a single table called “Asset”, aggregated across all available date folders.Actual behaviorInstead, all files/tables are returned, with what appears to be an "_<number>" suffix added for each additional date folder (e.g. Asset, Asset_1, Asset_2, etc.).I tried many setting combinations:Test 1: Exact filename, no wildcardsPath: parquet/ Inc

Hello, Technical: 20.10.67 using ODX (Updated: SQL Database not data lake)Connector: Cdata Ado.net provider for Json (2024)Settings: Source: Azure blob Data Model=FlattenedDocuments;Flatten Row Limit=1000000I have a situation with a odx transfer task failing and crashing the ODX due to memory.I need to jump in and help in a project where they need to get a very large json (85gb) into TX, because any previous attempts to ingest it fails. I ran a sample size to test (49mb) which resulted in roughly 550k rows and took 60s to run with a transfer task. One page (5000) takes around 200-300ms from looking at logs.If it is linear it would mean upwards of 900 million rows (we do not know the actual row amount) and it could take upwards of 30h if we assume linear scaling here. One easy problem was timeout time, which I fixed by increasing the ODX timeout from 2 hours to 24 hours during testing.Currently I can get it to run to around 6-7 hours but then it fails due to the ODX crashing with the fo

Hi, I am adding a mapping set (4 tables) to my table and then I get the “Source Table” column. After a deploy and execute the column “Source Table” have only a single dot in the column. I am expecting a table name from the mapping set as before... Whats wrong? Any suggestion? regards,Bjørn A.

Is the new TX Enhanced REST source slower than the old CData REST source?When we tested simple REST endpoints we saw the new TX source using 10x longer for the same identical job.Anyone have any experience with this?For reference we are running on TX 20.10.72.64.

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

In the new version 7257.1 What’s mean this symbol in some tables and fields? 

I have a TimeXtender REST connection to SalesForce. This specific REST API is a file api. This means that you have to send a request (in the form of a query) to an endpoint, after which the API starts to generate an export. When the export is finished, it can be downloaded via a separate endpoint as CSV.To extract this data with TX REST, I have set up a method with three endpoints per ‘endpoint’, this works as following:The first endpoint called _query sends a query via a POST request to a specific endpoint The second endpoint called _waitForComplete uses a dynamic value from the _query endpoint so that the _query endpoint gets executed first. The _waitForComplete endpoint uses pagination with a 1-minute delay to send requests to an endpoint that returns the status of the generation of the CSV file. Once the generation is complete, the _waitForComplete endpoint will return a JobComplete response which will stop the pagination. The third endpoint uses a dynamic value from the _waitForCo

Is there any documenation on how to get this set up?  I cannot find anything on the support site besides that the functionality is available.  I have set up things in my Snowflake account but TimeXtender refuses to create storage.  I have created the stage in Snowflake and point TX towards it and get this: Object reference not set to an instance of an object. I have triple checked all RBAC settings and the role assigned to my TX service account has what it needs. I can even see that after running import meta data it has created some folders in the stage.  But will not create storage or load data from my source data connections

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? 

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 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???  

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

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?