Jobs & Executions

The TX oracle connector drops and creates the complete table during export. Is there a way that we can control this behaviour and the table be not dropped ? This is because we need to move data from Staging Orcle to Main tables based on Triggers and if the table is dropped by TX then the trigger is of no use.

Can you pass project variable values at run time via the command line? We need to trigger the package and pass on user defined variable values that has been used in the package creation. Like a date that a user can pass whenever he intends to run a package.

So based on what I'm reading about TX, it seems to me that even if only say 5 records changed on a source file, TX loads the entire source table into a Raw table (all 40 gigs of it) and then finds the 5 records.Is there a way to get it to just pull the 5 changed records into TX?  My incremental executions seem to take about 50% of the time of a full execution even though there is little to no data change.

Hello,one of several incremental tables won't execute. upon execution the transfer fails stating "invalid column name " & name of the incremental column.The problem occurred in Version 19.2.7.64 and is still present after an upgrade and redeployment to Version 19.11.7.64.What I tried so far. I tried to change the column from Incremntal_date to id.Redeployed the full table configuration.Upgraded to Version 19.11.7.64.Help is much appreciated. Best regardsPeter 

Just for anybody interested: I just found out that you just update the _I table to some older values, to reload all data greater than the value you set. Previously, I always reloaded the full table in these cases. This is not necessary and saves me some time from now on.

Hello,I have the following setup for an incrementally loaded table:I would expect, that it loads all rows, with either an id greater than max id - 1000 or datum_post greater than max datum_post - one week.In fact, when I execute the query, it is not returning any rows. This is interesting, because removing the datum_post condition returns rows.Other tables with such a double condition (id + date) also work. I am wondering, whether it is necessary to have an index on datum_post in the source table? The queries can take quite a while on the datum_post field. The example query takes 2 minutes on the source database, but TimeXtender finishes after 30 seconds. TimeXtender says it is finished with "Success", but there are no rows.Also the following quer

Hello, Since a couple of days I created a second execution package to execute +- 10 tables, some dimension and 1 cube. After this execution the other cubes are not reachable, I need to deploy and execute them all to get it solved. Any clue why an execution pack would block access ? Thanks, Ronny

Hi,I have a source table in Navision which contains inventory data. The data is sometimes changed back in time due to miscellaneous reasons. I have so far handled this with change tracking in Sql Server and then I do a merge statement that either inserts new data or does an update on older data already in the fact table.So my question is how could I handle this in TX and do a incremental load?Regards Birkir

Hi all I recently changed the environment properties of the development environment to have the AX data source point to the live environment instead of the test environment. I hoped that executing (without deploying) the staging area would refill all staging tables with live data instead of test data (all full loads, no incrementals), but it didn't. In fact, what needs to be done, is deploying by manually marking all tables to be redeployed in the deployment screen, as nothing has changed according to TimeXtender. Is it possible to make the SSIS package connections dynamically looking at the environment properties (this way an execute would suffice)? Or mark the staging tables to be redeployed? TimeXtender version 16.8.1.64; project is using SSIS. Thanks!