Infrastructure & Networking

Recently we have been running into big problems with our production repository database becoming completely unresponsive after completing an environment transfer, actually leading to scheduled executions not starting the following night. It has happened twice in the last two weeks but never before during the 3 years that we’ve been working with TX. The issue is seemingly resolved having switched to a vCore model on the production repository, but we are at a loss as to the root cause of this problem. We have of course read all the relevant knowledge base articles/community discussions that talk about why the repository may become generally slower over time (execution logs have been deleted, yes) -however, for us it has not been gradually deteriorating but suddenly. Also, we believe our projects are not that big (see below) to warrant the export-import procedure. Setup TX version 20.10.25.64 Multiple environment setup (Dev + Prod), TX running on single Azure VM and all databases are Azur

Hello, TimeXtender 20.10.51 I’m looking for support with an issue we’re experiencing where execution packages are running but no tasks are being completed while causing 100% usage on the repository. After deploying to production, we ran a package manually and noticed it not proceed past the above step. The “current tasks completed” stayed at 0, and no data was being loaded, even after waiting up to 30 minutes. We tried running it multiple times, but nothing changed. Running individual tables worked fine. We checked the SQL database usage for the DSA to be sure, and it wasn't being affected—no data was loading as expected. While troubleshooting, we found that the repository (a standard 100 DTU Azure SQL database) was hitting 100% data IO and DTU usage. One query, in particular, was using nearly all the available resources. It was this query: (@ObjectId uniqueidentifier)SELECT [StepId], AVG(DATEDIFF(s, [Start], [End])) AS [AvgSeconds] FROM [dbo].[ExecutionPackageLogDetails] WHERE [Object

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. Application Portal SSMS Database How can I connect to existing databases for instance storage instead of creating new ones?

Hello, i am kind of stuck and hoping someone could give me an idea what am i missing to configure multiple environment setup that i have right now. I have 2 machines (call them A and B machines). A machine runs DEV and TEST environments of TimeXtender, B machine runs PROD environment. Current setup is as follows: Deployment path: DEV → TEST, then TEST → PRODEnvironment settings: This setup works, but sometimes i need to be able to deploy changes from DEV to PROD, bypassing TEST environment. My desired deployment paths would be: DEV → TEST and DEV → PROD. Since DEV and TEST environments are on the same virtual machine A and already can connect to machine B, i recognize that i would not need to change any firewall settings. As i configure environments my idea for steps is: B machine (PROD environment) - do nothing; A machine (TEST environment) - remove PROD environment, do not change anything else; A machine (DEV environment) - add PROD environment with Local port 10026 and Remote port 1

In the v20 release of TimeXtender, developers are able to access their ‘own’ data in the project repository db. By querying this manually or using the TX Dictionary project, you are able to gain a lot of valuable insights on your DWH implementation. I see that there already is an idea for implementing the TX Dictionary functionality in the new release. Is it likely that this will be implemented? If not, this could very well be a showstopper for migrating to the new release in my opinion. Enabling this through the TX API will probably be a lot of work for TX developers but this also limits flexibility. What other options are available for accessing our cloud repository? Would love to hear your opinion on this.

Hi, We have just installed TimeXtender on a VM on-prem and tries to start the applikation and the ODX Server Configuration. Both fails with the same error: Error occurred while determining instance version or during performing aut. upgrade: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) Details: SQL Server: '' SQL Error Number: 10060 I noticed that there is now server name in the error message. Is this supposed to be empty? The SQL server name is provided in the portal för both instances that have been created (One ODX and one MDW). We have no problems connecting to

Hi all! We are wanting to move the TX DEV environment to the PRD server. We are using 6221.1. All I could find is https://legacysupport.timextender.com/hc/en-us/articles/115001313583-How-do-I-move-a-project-from-one-server-to-another-. However this doesnt seem applicable to the new version. What is the best way to approach this in version 6221.1? Kind regards,Maarten

What would be the recommended compute tier for a project's repository database? (TX v20.x) I believe the current default on Azure is General Purpose 2vCores, however looking at the utilization this seems to be excessive. Does anyone have experience with running the repository on a Standard DTU database? Thx

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?