Windows-based server software installed on a centrally located physical or virtual machine. This software orchestrates the ingestion of data from various sources. This separates data movement from the desktop software, while ensuring data never leaves a user's environment.
2. The ODX Storage
A SQL database or Azure Data Lake where raw data is stored after ingestion from sources. By storing data in its raw form, it can be used for later analysis, or retrieval.
3. The MDW Storage
A SQL Database or Synapse Dedicated SQL Pool where data from multiple sources is cleansed, transformed, and consolidated into a single version of truth.
4. SSL Endpoints
A subset of related data combined into a single model or "mart". This model can be exported to multiple endpoints such as Power BI, Qlik, Tableau, Analysis Services, or CSV.
5. TimeXtender Portal
A web portal handling the administration of your TimeXtender Data Estate. Instances hold the storage connection details as well as maintain the configuration information implemented in TimeXtender Desktop.
6. TimeXtender Desktop
Windows-based Desktop-client software where each instance can be configured & implemented through a single, integrated user-interface.
What's an Instance?
Instances are the metadata components of your TimeXtender Data Estate.
They store the connection info to the associated target storage.
They contain the metadata for how this area of TimeXtender is configured. (e.g. What tables are selects in an ODX Data Source, What relations & transformations exist in your MDW, etc.)
They maintain versioning, so each individual instance can be rolled back a previous version.
Any instance can be copied to another instance of the same type. Allowing you to migrate your instance configuration to another storage type or environment.
All credentials entered into the portal are protected with 256-bit AES encryption.
When working in a sandbox environment, the Desktop and Server software can be installed, run, and controlled all from the same machine.
However, in production-ready setups, multiple concurrent users are necessary. Ideally, each client runs their own local instance of TimeXtender Desktop and connect remotely to the ODX Server.
Please note: With a client-server setup, the ODX Server IP Address or Hostname must be "reachable" by each client machine.
AdventureWorks is a commonly used sample dataset that closely represents common online transactional processing (OLTP) systems. It is based on a fictitious manufacturer and distributor of bicycles, outdoor equipment, and apparel. In this training we will perform common extract, transform, and load (ETL) techniques on this data. To become more familiar with the dataset, click to expand and explore the AdventureWorks entity relationship diagram.
TimeXtender supports multiple environment deployments that allow developers to create separate environments for development, testing, and production. These environments can be comprised of separate instances that can then be related to one another.
For example, a common configuration is to use three (3) environments, representing Development, Testing/User Acceptance, and Production, (a.k.a “Dev, Test, Prod”). By using three environments, we experience several benefits.
Development (“dev”) is where developers build the solution, and may have many requests or work items to work on, at any given time. When the features or improvements to the data estate are “completed”, the work is “promoted” to the Test Environment.
Testing (“test”) is where the prod-ready version of the data estate is tested by the developers, consultants, or QA Engineer. This ensure that a deployment to Production will be smooth for the users, and that all features are STILL working as expected. Documentation is a good idea at this stage, if not already done.
Production (“prod”) is undisturbed by building and testing, by planning new deployments at low usage times during the “business week”. This is to allow Data Users to have an uninterrupted access to reports and analytics.
create New enviRoNment in Portal
Open www.app.timextender.com in your web browser.
After successfully logging in select Environments from the drop down menu on the top right.
Click on Add Environment
In the pop-up fill in the Name, Description, and select the instances to be added in the environment.
Once the instances are added you can view them in the environment page.
To promote the changes, select the arrow next to the instance containing the changes that are to be promoted.
In the To dropdown select the instance where the changes needs to transferred to.
WARNING: Only tasks relating to one ODX instance can be added to a job. In other words, tasks from different ODX instances cannot be added to the same job.