Ask general questions
Good DayOne of our clients who use TimeXtender (20.10.47.64) experiences a Server Memory issue in Production when IT Operations opened the Multiple Environment Transfer Window. IT Operations reported that the window took ages to open but did eventually open. The Network Administrator did then have to hard reboot the server in order to get it to respond.Attached are the messages reported within TimeXtender.
Hi,I am currently working in TimeXtender Data Integration (version 6766.1) and would like to view the relationships between my tables. However, when I access the “Relation Diagram,” I do not see any relationships—neither between tables across different data areas (e.g., DSA and MDW) nor between tables with lookup fields.Is there a specific setting I need to enable to view these relationships? The data lineage for specific fields is functioning perfectly.
Hi,I previously obtained my TimeXtender Solutions Architect certificate. How can I get the badge to show up in the community? Kind regards,Ludwig
Hi,Is there a way to view the data lineage for tables populated using the Custom Table Insert method? When we select the “Data Lineage” option for a column in a Custom Table Insert table, it only shows the data lineage with that table as the source, rather than displaying the tables used within the Custom Table Insert itself.I saw that this post had a similar question like mine, but I couldn't find an update about it: data lineage for custom table insert | CommunityThank you in advance!
Hi, I am using TX 20.10.45.64. Can you tell me when support for this version will end?
Hi all, We implemented a semantic model on Azure, granting access to our users through Azure AD groups. By creating roles that include Azure Tenant IDs and enforcing Row-Level Security (RLS) dynamic settings.However, we’ve encountered a challenge: when changes are made to certain fields, the RLS configurations can sometimes fail to enforce restrictions properly. This can lead to unintended access, where users in an AD group suddenly find themselves with visibility into all data, rather than the limited data they should see.To address this, we’re exploring ways to implement a more restrictive access model within the RLS role configuration. Specifically, we’re considering options that would prevent any data visibility until RLS settings are confirmed to be operational.Proposed Solution:Initial Data Restriction: Until the RLS settings are validated, no users should have access to any data. Validation Checks: Implementing a validation mechanism to ensure RLS settings are working correctly
Dear Sir,The migration Tool is giving me this dialog.Is there anything I can do ?Regards,Arthur ExecuteBulkInsertQueryStep Failed at Step BusinessUnits.Adding to table [dbo].[ODXConnects]Violation of PRIMARY KEY constraint 'PK_ODXConnects'. Cannot insert duplicate key in object 'dbo.ODXConnects'. The duplicate key value is (47f7cfb0-0337-40bc-b508-79172aec7258, 99999999).The statement has been terminated.Details:SQL Server: 'sql-instances-prod-002.database.windows.net'SQL Procedure: ''SQL Line Number: 1SQL Error Number: 2627Violation of PRIMARY KEY constraint 'PK_ODXConnects'. Cannot insert duplicate key in object 'dbo.ODXConnects'. The duplicate key value is (47f7cfb0-0337-40bc-b508-79172aec7258, 99999999). ...
Hello,I have created a semantic model of my project which is implemented as SSAS endpoint. Users usually connect to it through excel and browse the model.Fact tables are connected to dimension tables using ID key. I want the fact table to be filtered based on values on one of the columns in dimension (fact table has millions of records and there are around 500k distinct IDs of the dimension within it).Question is - if i apply row-level security on one of the columns in dimension - will it apply that to fact records as well? Or i must specifically apply the RLS onto the fact itself?Thank you
Wondering if Timextender version 20.10.44.64 support the new TLS 1.2 version
Instead of creating a database from within the TimeXtender interface with the Create Storage option suggested in the standard procedure, I want the TX instances to be connected to exisiting databases on an SQL server. I want to do this for ODX as well as MDW instances. The SQL login to be used by Timextender is not allowed to have sysadmin or dbcreator privileges on the SQL Server, and can therefore not be used to create the databases. If I press Create storage with the name of the existing database specified for the instance in the portal, I get an error message saying the database already exist, but with no visible option to utilize the database. ApplicationPortalSSMS DatabaseHow can I connect to existing databases for instance storage instead of creating new ones?
Hi everyone, we're migrating from onprem to an azure SQL db. (version 6x).What would be the approach to migrate history tables? Can't find much on the forums that fits our usecase.
Hi all,our customer has tables that are SCD2 historized with valid_from and valid_to columns and a “version” column, where 1 is the most recent entry, 2 the next older entry and so on.Is there a possibility to load these tables into TimeXtender, preserve the history (make it useable for TimeXtender) and continue historizing in TimeXtender, so that they can turn off the historization in their source table?
Good morningWe used the migration tool to upgrade from 20.10 to the saas version.In the comparison of records in the MDW we miss out on the custom data which we use to insert -1 and -2 records.Old situation: After migration: This is very inconvenient as this requires adding all custom data once more.
Dear Sir,I am looking for a sql query on my local sql repository to create a list of all my datasources in my projects.I am using v20.10.45.Thanks in advance.Regards,Arthur
I would like to know what the best way of working is if you have multiple environments (DEV, TST, PRD) with the new version. In the old version you had to open a different project repository that you could set a different color, so you were always aware on what you had open.In the new version all the environments are available in the desktop and a mistake is very easily made on what environment you open. Names are also shared between environments so you never know what DSA you have open.Love to hear some comments on how other customers are working.
Good morning,We upgraded to 6675 version and are now testing a deployment to snowflake.The tables based on full load mappings deploy well (with our without simple mode)When deploying tables who are based on an incremental ODX tabel we recieve an error on the syntax of the usp clean procedure TimeXtender wants to create in Snowflake.The script TimeXtender creates starts with:CREATE PROCEDURE "HIST_ETL"."usp_ReaturnTM_DimRentableUnitCommercial_Clean" :DWBATCHNR INTWITH RECOMPILESnowflake doesn’t expect the : and returns:Syntax error: unexpected ':'. (line 2)Is this a known issue and if not, I hope it can be added to the wishlist with TimeXtender features that need to be made available against Snowflake storage.
I did the upgrade to 6675.I can login to the new version but my colleagues get the error below.We are all admins on the vm’s.
Hello!I am using Timextender to get MS Dynamics data to an Azure SQL DB.I would now like to use the Fabric Mirrored Database function (https://learn.microsoft.com/en-us/fabric/database/mirrored-database/overview) to integrate the tables from the Azure SQL DB in a Fabric Warehouse. However I get this error upon execution in Timextender:Cannot truncate table 'dbo.D_Date' because it is published for replication or enabled for Change Data Capture. Is there a way around this or will the Fabric DB mirroring function not work with the Timextender/Azure-DWH tables?Thanks for any advice!
Dear Sir,I am working with a client to migrate TX to latest version (from legacy to latest).Now, they want to migrate to a TX Standard license, wich will give you 4 Datawarehouse Instances.Question: Is is possible in this scenario to run 4 Datawarehouse instances in Development and 4 Datawarehouse instances in Production in the latest TX version. All together 8 dwh instances. Is that allowed within the TX Standard license package ?Or do we have to configure 2 dwh instances in Development and 2 dwh in Production to meet the TX Standard license requirements (4 Datawarehouse Instances) ?Hope this makes any sense 😆Thank you in advance for looking into this. Regards,Arthur
Dear Sir,I am working with a client to migrate TX to latest version (from legacy to latest).Now, they have a lot of Data Exports (CSV files) in their projects, about 50 all together.Client wants to migrate to a TX Standard License, wich will give you 18 Data Product Instances.Question: Does a Data Export (CSV files) count as a Data Product Instance ?Does my client has to move to a TX Premium license ?Or is there an alternative for this.Many thanx for looking into this 😀. Regards,Arthur
Hello,We are still running on TX 18.6.8.64 version and SQL server 2014.Now they want us to upgrade to SQL server 2022 so it makes sense to also upgrade TX. Questions:can I upgrade from 18.6.8.64 to latest TX version in 1 go ? is SQL server 2022 working fine with latest TX version ?Thanks,Ronny
When deploying the project in the PROD environment (through multiple environment transfer) we get the following error.: Source: System.Memory Type: System.IO.FileLoadException Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at System.MemoryExtensions.AsSpan(String text) at Microsoft.Data.LocalDBAPI.GetLocalDbInstanceNameFromServerName(String serverName) at Microsoft.Data.SqlClient.SqlConnectionString..ctor(String connectionString) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous) at Microsoft.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions) at Micros
We're experiencing projects to open very slowly using TX 20.10.38 (we're above version 10000 of the project) Is there an easy way to remove old versions of a project ? We are using multi environment with global databases, and don't want to go through the export, create new repo DB and import hustle.We're also trying to delete the logs, but deleting them from within TX seems to take forever.
Looked for this in the documentation, but couldn’t find it - is TimeXtender 20.10.X compatible with Windows Server 2022?
I have setup an Execution Package and am running a number of Perspectives in the order they need to build in the project. I then call 2 External Steps, which are Execution Packages in other TX Projects in the same environment. I am having an issue where when a step fails in the project, the build then continues onto the External steps whereas I would like the entire package to fail. I thought this would be accomplished by selecting the FailPackage action on Failure Handling but it is not working. Do I need to set this up a different way to get this to work?(I have hidden sensitive data in my screenshot)
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
