Prepare

Hi guys,Somehow I am unable to create a job for my semantic models or my datawarehouse/ data area. I can’t select the model when I’m trying to add a new job.  

Good morningI am deploying a specific table with history (mostly type2) to Snowflake.However in the generated script the semicolumn is not placed correctly (after the ; some additional ‘and’ clauses are added). This results in an error creating the data cleansing procedure. I added the script in the attachment.Can you please have a look.

This problem arrived after the issue with SNK is resolved. I am not sure if the two cases are related in any way but that was the last change made in TX.I am trying to figure out why data clensing is taking so much time. It ultimately ends in time out:Error during Data Processing for Table: DSA.FACT_TABLE_A at: DSAExecution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.Operation cancelled by user.Warning: Null value is eliminated by an aggregate or other SET operation.The wait operation timed outStored Procedure: [DSA].[usp_FACTABLE_Clean]Parameters:@version = 2177Line number: 0Details:SQL Server: 'TEST-SQL-SERVER'SQL Error Number: -2The total number of rows in ODX are 9 664 965. It shouldn’t take more than a few minutes to transfer and data clens ! 

Hi Team,We have a data provider for which we need to connect to MySQL. We want to incrementally bring data from the source, but the problem is that all the columns in the table are of the string data type. This prevents us from setting any incremental logic on the date column, which is currently stored as a VARCHAR(8). I tried casting the column to a date format, which works in the query tool, but when I try to add the query table, the option is disabled. I am using Mysql 5.1 client data source.Could you please suggest how I can achieve this?

Is it possble to create a table based on CTE in timextender, or how would you do it? 

Hi everyone, back again with another issue.  We have now setup our ODX with storage account as storage layer. refreshing it sometimes breaks though. I'm getting 404 error, path can't be found. This happens with transfer all option. When I run the set of tables one by one, everything seems to be fine. I saw 1 more post like this for oracle, where the connector got updated. We're using an older version so I suppose can update the cdata connector and try again. However: the weird thing is that this also happens with ODX to DSA. Any clue how this is possible? Path does not exist, but I can find it in the storage account. 

Dear all, We have tx instaled on Azure and on premise. The version we are using is 20.10.52.64. how is it possible that on the onpremise we can use the custom data selection rule and on Azure this screen is not appearing in the DSA?The issue we are facing is that we want to limit that data we want to load in the odx when the raw table is being executed. Therefore we want to set a customized data selection tule on the mappings.Why this option is not in Azure but it is there on the on premise?We want to load / keep all data in the odx server and make a data selection rule in the DSA..Imagine we are migrating from on premise and we want to show only 15 months of data instead of  10 years. Only if the customer is asking for it we will load it.  This is working on the on premise perfectly.Now that we are migrating from on premise to azure we are missing the most used data selection rule. And the advised work around 

See the screenshot. in the mapping you can see all odx sources with the correct name (ODX(BEBOO1): bronze.blueyonder_wms.DSCMST. However when I go the the field mapping The name for each source is now called local host????For trouble shooting purposes when missing a mapping. It will create a work around for us, because we have to click on the table to see all mappings on the right side then you have to go on be by one.  why the name have changed on a the field mapping? possible to have a fix for this? 

Hi all, I'm looking at making the right keys in our database model. I've been reading some topics on the forum but haven't found a shared opinion on the best practice. Super natural keys Advantage: Easy to use.   Disadvantage Huge performance impact. According to some topics reloads can increase in time from 3 till 30 minutes.  Their are relations in reloading the tables in the correct sequence. TX will calculate this sequence, however their is an increased change of circle references. Hashed Keys Advantage: Easy to use.  Should be faster than SNK. It doesn't need a look up to the keystore.  Disadvantage: Change on duplication of keyus is limited to a minimum Source: https://stackoverflow.com/questions/297960/hash-collision-what-are-the-chances Look up DW_Id from different tables Advantage: Able to make all joins on last layer. Easy to use.  BIGINT in keys, is better than VARCHARS in keys.  Disadvantage: It will cost the simple mode in transfering data from data area X

Hi again I have a table with the following values: I want to add the [No] from the first line (101) to all the other lines .. therefor I thought of making a SQL like this the following. I ​​​​​​Why is it my nested Select doesn’t work ??or are there a smarter way than what I thought of doing ?

I often get this pop-up when i Execute a table or a view. It could be either a new table/view or an existing.I get it in DSA and MDW. Dont remember getting it in ODXWhy do i get it?What happens when i click on Yes? What happens when i click on No?  

Hi alleI’m all new to timextender so please bare with me .. I have 2 tables which I have to join but there are duplicate values in both tables .. in one of the tables it’s ok if I somehow made an distinct data selection to it .. but I don’t know how .. I also looked into making a bridge table, but that wouldn’t at first hand solve my problem .. Do anyone have a sugestion on how I could/should make a relationship between these to tables or how I could make a data selection rule that somehow made an “group by” or “distinct” selection ?

Dear Sir,Our client is trying to promote/release their DataWareHouse from DEV to PROD.They are using the Environments page (https://app.timextender.com/data-estate/environments) in the Portal and after a minute or so this Error pops up:“failed with the error 'SQL errored whilst updating target tables”See Word attachment for screenshot details.Client is using TimeXtender version 6675.2Their is no detailed information for this error, so can you please give us a hint where to look for, to solve this.  We double checked all database connectivity for DWH and ODX.No luck so far.Please assist. Regards,Arthur

After upgrading to TimeXtender 6675.1, we are experiencing some errors when executing custom table inserts. The error message is ‘The given ColumnMapping does not match up with any column in the source or destination’.As it turns out, we have a few CTI's where the target column name was spelled with a capital letter when in fact the column name was with a lowercase or vice versa. This was never a problem but we had to correct this in the newest 6675 version. Has there been a change in where the CTI's target columns are now case sensitive?

I want to join 7 tables and fetch columns from these tables and make a different table from it, so is it possible in Timextender without creating a custom view?

I have a weird issue in my new TimeXtender project, where my tables in my dwh layer won't load data from the Business Unit. I have a very simple setup to start with. I have one business unit which loads a couple of tables, and the Bussines unit configured to store data on our “VMTXTD001” server in a database. The Datawarehouse uses the same database as the Bussiness Unit and should load from that Business Unit. But when I execute the DWH layer I get this message for all tables:  Start Time : 4/19/2023 4:14:08 PM End Time : 4/19/2023 4:14:10 PM on server: VMTXTD001-Execute Execution Package Default 'Failed'    Invalid object name 'VMTXTD001.dbo.DM_CRM_Replica_dbo__CustomAccount_DSA_dsa_test_T'.        Details:        SQL Server: 'vmtxtd001'    SQL Procedure: 'dsa.usp_CrDM_dsa_test_CRM_dbo__CustomAccount'    SQL Line Number: 12    SQL Error Number: 208        Invalid object name 'VMTXTD001.dbo.DM_CRM_Replica_dbo__CustomAccount_DSA_dsa_test_T'. To me the issue appears to be that TimeXtend

Dear Community,When I create a view in my data area MDW from a table which is in my DSA (=> I drag the table from my DSA are to the views in the MDW data area), the view auto parameterizes (which is great). I deploy the view in the MDW, read view fields and preview it. (all is still great).When I release this to my next layer (PRD) I suddenly get a erroer previewing the MDW view. When I check the view in the PRD MDW the parameterization is all gone.Have you encountered this? Is there a solution?Thanks= Daniel

I am loading a fact table from a staging table, both are regular data warehouse tables. When I create a data selection rule on the mapping table, I'm unable to select the conditional lookup fields or the system fields from the source table:  TX Version is 6590.1. In legacy TX, it is possible to select the conditional lookup fields and system fields for creating selection rules: We have implemented a workaround where we create an extra field in the DSA table that has a transformation that fills it with the value of the conditional lookup field. In turn, this extra field does show up in the selection rule fields because it is a regular field. But this is not a very nice or future-proof solution.Is this an intentional change and if so, can you explain why? Or perhaps this is a bug in TX SAAS?

Hello,I can’t seem to find out how to create a variable holds the name of the data warehouse environment in new TimeXtender (6626.1).I’m thinking of the name of the environment as defined in the portal, not the name of the data area.Thanks!

Hi team, I have a table in a data-area that is filled by a single mapping set, in this case containing 7 tables. Because we discovered some differences between the fields we need from each table, I want to convert it to a normal mapping. I tried to do this via ‘Smart Synchronize’, but it is only working for fields that have not had a name change. In other words, when choosing to smart synchronize a single table onto a table with a mapping set, it seems to perform a ‘Synchronize (only existing fields)’ instead of looking at the name of the fields in the mapping. Is this expected behavior?Kind regards,Andrew

Hi,I have a very regular table that is loaded from a SQL Datasource. The table has a little over 3 million records and the following definition:  Nothing out of the ordinary as you can see. The table is loaded with the ODX with an incremental selection rule on te mut_dt column. The ODX load works fine; loading the table full or incremental is no problem and the data is stored in the container as expected within 1 or 2 minutes.However, when I drag the table to the DSA data area and load it there, something strange happens. Loading the table to the DSA hangs after 900.000 records are inserted into the raw table. We have tried waiting for several hours, but it just hangs there and nothing happens. Other tables from the same source load fine to the DSA.Data source version is TimeXtender SQL Source v 19.1.1.0 (but load from source to ODX works fine)ODX and TX version is 6590.1 .

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

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.