TimeXtender Desktop Q&A

One of our client's has a problem with the version mismatch between odx and desktop application. They are running on 6645.1 odx but some of the desktop versions are still on 6626.1 they get an error that the odx version is locking them on 6645.1 but it's expecting 6626.1. Is there a workaround for this or a fix? or is this a bug? I know the ‘easy’ solution is that all the desktops versions should be updated at the same time for everyone ones you also update the odx but that's not always possible.

Hi all,I need to extract data from a huge table in SAP (KONV) based on a subquery from another extracted table (VBRK). Any ideas on how to solve this using the XtractIS? I can’t use quey tables on this type of connector and I tried to put the subquery in the filter rows filter for “in list” which also didn’t work either. Any more ideas how to solve this? Many thanksKai

Hello,TimeXtender: 20.10.40.64ODX: 20.10.31We have an issue on certain source where transfer tasks result in “completed with error” or “failed” in the ODX.This lead to the question if there is anyway to capture this without going into the ODX and manually checking every transfer, as there is no way to set up any notificaiton.We need to someone capture this, as the loads within TX will run as usual without failing but not get new data from the sources in most cases. Has anyone found a solution to streamline this? Within Timextender or with a external solution?Thank you,Victor

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

I have been playing around with the on-demand load and set up some SQL Sources to use this. When I right-click Execute a table in MDW that loads from an on-demand source (TimeXtender SQL Source, ADO.Net transfer) I do not see any new extract to ODX - so I decided to run a Job: I subsequently right-clicked a Job that reloads my MDW layer and chose Execute. If I try to Execute again I get a message “The job xxx is already queued”, it does not ever seem to Execute the job however.Is there somewhere where I can see the job queue?

I am working in a project and the execution is to mach slow,  It has take 35 minutes for 5 tables, that all of them has 10000 rows.    

When promoting a Semantic Model (copy to instance), are the Roles and especially the users/groups within the role in the model also copied to the other environment? In legacy TX we were able to grant a role to different users/groups per environment, but in the new TX it seems to be the case that we have to change that after promoting?

Hello, I am using ODX server 20.10.47. I would like to limit the amount of records loaded by implementing following filtering rule on column [perakt] among others:LEFT ([perakt],2) > 20I am trying to achieve this in following way using “Filter Rows” options on data source but it does not work:Also if i click OK and load the data, the 2 upper filters are not applied, just because the 3rd filter does not work.Are there any ways of achieving this through “Filter rows” functionality? Or the only option is to create a custom query table?Thank you!

Good Day,  We are receiving the following error messasge: Finished executing project 'COMPANY' Execution Package 'Client execution'Execution failedStart Time : 5/24/2024 7:57:22 AM End Time : 5/24/2024 7:57:22 AM on server: NAME-Execute Execution Package Client execution 'Failed'    The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.        Details:        SQL Server: 'NAME'    SQL Procedure: ''    SQL Line Number: 1    SQL Error Number: 242        The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.    Module: .Net SqlClient Data Provider    System.Data.SqlClient.SqlException       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)       at System.Data.SqlClient.TdsParser.TryR

In my source table, I have a column called [lastSync] that is varchar.In my history table I have last_sync as datetime.Currently the only way that I know of how to solve this is to eitherCreate new Custom field [last_sync] in my source table that includes TRY_CAST([lastSync] as DATETIME) The problem here would be that I would need to change my Source table from Simple mode. I would like to keep the simple mode table. Data redundancy as this specific column is stored twice. Create a new Custom field [lastSync] in my history table to accomodate the data before [last_sync] uses Custom Field Transformation to cast to datetime. The problem here would be redundancy as I’m storing the same column twice over a long period. Of the two I would prefer option 1.Is there no way to do this on the fly, so that data is converted when transferring data from the Source Table → History Table?  I’m Using TimeXtender Business Units 20.10.32.64

Hi, Since we upgraded to 6626.1 our TimeXtender SQL Data Source (18.0.1.0) type data source has been failing. We believe it is because 6626.1 expects a TimeXtender SQL Data Source (20.0.1.0). This either is a bug that needs to be fixed, or in the product update log / in the portal there should be some warning about this. If this was mentioned somewhere in a product update please share the link to the article.   

Good morningYesterday on the development vm I created a job to be executed on a production vm (which has the related instance marked  in the execution server). However it did not run last night.Is it necessary to log in in TimeXTender desktop in the production vm for the job to become active on that vm?

Hi Everyone, I was playing around with Clustered Column Store indexes to see if it would help increase performance of reading data from our DWH. It didn't help so i wanted to revert to the old situation by removing the index. However, on deploy i get an error message and i'm not sure i'm doing something wrong here.I basically just created a Clustered Column Store index, deployed deleted it again and deployed. On the last deploy i get this error message (so the problem is in deleting the index somehow):An error occurred during update table. See exception details for the failing object: Exception occurred during execution of RebuildHeap process. An exception occurred while executing a Transact-SQL statement or batch.. failed for Table 'MDW.FactHistStockManagementData'.This is not a valid data compression setting for a columnstore index. Please choose COLUMNSTORE or COLUMNSTORE_ARCHIVE compression. I've ran the profiler against the deployment and it seems the error is coming from this sta

Hi,In TimeXtender Portal under Data Estate → REST API web servers, the description suggest that you can install the web server as an Azure Web App. When you run the installer, it tells you that you need IIS and ASP.NET Core. This indicates an install procedure for running the REST Web Server on a VM.What is needed to set up the TX REST Web Server as an Azure Web App?Best,Erik

I have a database role on my DSA which cannot be adjusted or removed. When I delete the role and deploy I get an error: “An error occurred during drop role. See exception details for the failing object: Drop failed for DatabaseRole 'SBIE'. The database principal owns a schema in the database, and cannot be dropped.”.What does this mean and where should I look to solve this issue. In the end I want to have this database rule deleted. Perhaps I could do it outside TX, but I want to check the options in TX first.

When having an historic snapshot table in TimeXtender MDW, based on a table insert, I need to limit the table somehow to prevent it from growing too large. I want to limit the [Date] field for only 1 year of data. Because it's based on a table insert, there are no fields available in the table to use for a table “Data selection rule”. I can only place a data filter on the table insert which only has data of 1 day.My historic table works like this: Actual table (snapshot of today) Historic table (table insert, daily, of actual table, so it stacks up the daily snapshots)(TX version 20.10.43.64)

As you know in TX you can have a lotof data areas that in the SQL data base are schemas.In SSMS you can group the objects in folders based on their schema using this addon:https://github.com/nicholas-ross/SSMS-Schema-Folders Hope this helps. 

I have a job that reloads a DWH instance that seems to be stuck on ‘Active’. This job is months old and may have been killed by a VM being shut down automatically.  This job blocks executions with a ‘Job already queued’ error.Is there any way to remove this from the queue?  

I'm using a FireBird database connection over ODBC.Syncing gives me the following error:System.ArgumentException: Column 'TABLE_SCHEMA' does not belong to table Tables.There is a column TABLE_SCHEM (no A). Can I override this somehow?Key Value Is Sensitive Schema Name TABLE_SCHEM false This does not work as additional option in the Data Source TimeXtender Desktop 6536.1 Kind regards,Thijs 

Hi, One of the improvements of the that is stated for this update it says the following for the tabular model.“We've improved the Tabular model generated by the Tabular semantic endpoint to have better efficiency and reduce the size of the model.” Could you elaborate a bit more how it is more efficient and how you reduced the size? For us the size is especially important, since we have a 16gb limit with our ssas. Could you elaborate if you changed the encoding hints, since I do not assume you are changing any datatypes or something like that. Or did you guys mean that the processing of the tabular model has been improved, and the size it takes during processing has been reduced?In any case, I wrote another question regarding Tabular model size, and DirectQuery mode. Maybe here the timextender team or anybody else can give guidelines / best practices to reduce the size of the Tabular model as much as possible.  

Hello,I have a data export object/task. I have created an execution package that runs this export. When I start this execution via a schedule it fails with this error (table does not exist):Execute ReaturnPortefeu:Info:Initialized -Execute ReaturnPortefeuExecute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_Export:Info:Initialized -Execute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_ExportFill Data Export Table 'vw_ReaturnPortefeuille_Export':Error:Failed -Fill Data Export Table 'vw_ReaturnPortefeuille_Export' 'Failed' The table vw_ReaturnPortefeuille_Export does not exist!When I start the execution manually (right click and execute) it works without issue.Execution logThe source table for the export is a view:Source tableWhy does it fail when scheduled and not when run manually?

Hi team, TimeXtender allows adding parameters from a different table to a custom field in a semantic data model (Qlik). The resulting syntax/qlik script combination is always broken.When using adding a custom field parameter from a different table, TimeXtender fully qualifies the Qlik syntax regardless of the settings. The resulting syntax on the Qlik side will no longer match the syntax in the views created by TimeXtender:Qualified setting:Fully qualified setting: The resulting Qlik Script:"Sales_Targets":LOAD"KPI", "Target", "DIM_Boekdatum.DayName" AS "Test";SQL SELECT"KPI", "Target"FROM "Test"."dbo"."Test QVD_SLQV";But the view has the following syntax:CREATE VIEW [dbo].[Test QVD_SLQV]-- Copyright 2011 timeXtender a/s-- All rights reserved---- This code is made available exclusively as an integral part of-- timeXtender. You may not make any other use of it and-- you may not redistribute it without the written permission of-- timeXtender a/s.ASSELECT [KPI] AS [KPI] ,[Target] AS [Targ

I’m using Timextender version 6521.1 and I get an error when using hard deletes on a incremental table. If I choose no deletes it works just fine, soft deletes also throw me and error. As far as I could tell from these notes incremental loading should be fully supported. Things I have checked:Primary key on the table in the ODX Incremental load is setup in the ODX Incremental load is setup on the Snowflake table. I’m not quite sure if this is just a bug or I missed something obvious. This is the first table i’m trying to load incremental in Snowflake. This is the error it throws at me:System.AggregateException: One or more errors occurred. ---> Snowflake.Data.Client.SnowflakeDbException: Error: Error parsing the parquet file: Invalid: Parquet file size is 0 bytes  Row 0 starts at line 0, column   If you would like to continue loading when an error is encountered, use other values such as 'SKIP_FILE' or 'CONTINUE' for the ON_ERROR option. For more information on loading options, plea

Hi,We have been using ADF for transferring data from our ODX storage account to Azure SQL database for a long time but now our manual and scheduled reloads get stuck in ADF.It looks as if TX does not pass the runtime to ADF. This is required because our storage account is behind a private endpoint so we need to use an IR that resolves in our VNet in Azure.Do you have any idea why the runtime does not appear on the pipeline? As you can see there is no runtime assigned to this run:  Normally the runtime appears in ADF:  We are on TX 20.10.45 by the way.Would love to hear from you!

Hello,We are currently utilizing the new TimeXtender REST API 6.1 and leveraging its built-in paging feature to connect to an external REST API. We're not using an RSD configuration for this setup.I've encountered a challenge with pagination, specifically with the use of a parameter named "Cursor." This parameter is critical for the pagination logic in the API we're connecting to. Each row in the data returned by the API has a unique Cursor value, but for pagination purposes, only the first Cursor value from the current page should be used in the subsequent POST request to fetch the next page.Here’s how we've set up the Cursor parameter:Name: cursor Type: XPath Value: /TX_Autogenerated_Root/TX_Autogenerated_Element/data/arTransactions/edges/cursorThe issue arises because I need to ensure that only the first Cursor value from each fetched page is used in the pagination post body for the next request. I'm unsure how to configure TimeXtender to utilize only the first Cursor value for this