Infrastructure & Networking

We would like to possibly switch from ADO.NET to SSIS.  At the moment, both the TX application (ODX is not being used) and the SQL server are on the same box using ADO.NET.  We want to split off TX to its own server and use SSIS instead of ADO.NET.  Has anybody done this and can share the high level steps?  Or even how you think it might be best accomplished?  Specifically, once the application server is up and running with all the pertinent software, how would one make this transition?

Good morning, We have a need to export a subset of data from our current Azure data warehouse to an AWS target. Does TimeXtender currently support AWS as a target? If so, could someone point me in the direction of some documentation on how to configure it? Thanks, Chuck

We have multiple TimeXtender projects that use the same databases for their ODX/DSA/MDWs. What is the best way to use tables from one project in another one of the other projects? "Add External SQL Connection" seems to be an option, should this still be used if the table we want to connect to is in the same database?

I have a separate Test and Production environment. Currently each environment has its own ODX database. But some cloud API source systems charge euros for loading records through an API connection. I’m therefor checking how I can limit the data transaction on the source systems. Also we only use production data in Pest and Production. Since we use Azure I don't want to load all the production data twice. One way is to use 1 shared ODX for both Test and Production. Then I only have to load the source data ones. I can think of the following options: 1. Use the ODX server I've tested the ODX server but I can't use historic tables and incremental loads don't work on most API connections. I also encountered limitations on a firebird SQL data source. So the ODX server doesn't seem like a workable solution 2. Use an external ODX business unit A external business unit works. But how can I use a single external ODX for both Test and Production as these environments run on different project repo

  Due to cost of servers, it would be beneficial to have both a developer and a production on the same server. Is this possible right now? The manual doesn't explicitly mention this. If it is possible to run both environments on the same server, do they need different SQL server instances or can they use the same instance?     

I'm currently migrating an Azure MI solution to ADLS Gen2 and Synapse Analytics. The migration includes remapping all DSA table ... instead of using an old ODX, DSA will now use an ADLS Gen2 on ODX Server. Mapping tables bring all data source fields across ... it would be nice to have the usual option to only synchronize existing fields as it's a lot of fields to delete when getting the entire data source table.

Hi ,  our DH setup consists of multi-layered datawarehouse whereas BI client (tableau ) only interfaces the upper tier: MDW DWH. Having semantic layer for each dashboards (we have quite a few), we would like to move out of the single core TX project with multiple semantic layers to a project for each dashboard (semantic layer).  By doing so, we can make sure that each developer works on his own project without "stepping on each other toes" (I'm aware of collabaration features of TX) and keeping our core project unharmed.  So, the challenge is how to reuse objects created in the core project (preferably VIEW to reduce space/redundencies) in entire new project (same server/database) My approach was creating a new project, add MDW datawarehouse and then utilize External SQL Connection to connect to the same DWH (transfer type connection). I've also created a seperate database schema with valid behaivor.  The problem we ran in was that designated table was the same as similar table in the

I have used the data export tool to export to .csv files. However I can not do it straight from the Business Unit. Is that a feature that can be added? Or maybe not included in client license. The client wants a few tables from source to be transfered to Azure Data Lake as a csv file and do some tranformation there.