Maximum Results with a Minimum of Coding
TX DWA was born out of frustration with the tedious process of coding a data warehouse “by hand” and our goal is to minimize the amount of code you need to write to get a fully featured and high performance data warehouse up and running. At the same time, we want to make the administrative tasks, such as transferring from a development environment to a live environment, as easy as possible. All in all, we want to make developing a data warehouse as easy and enjoyable as we can.
Drag and Drop Interface
The central feature of TX DWA is the GUI that enables you to create your data warehouse by dragging and dropping tables, fields, transformation, joins and all the other elements of a data warehouse. Projects are stored in metadata that TX DWA converts into T-SQL and MDX code on deployment to the SQL Server.
With each full deployment of a project, you effectively get a data warehouse solution coded from scratch using performance-enhancing techniques that would be hard to implement “by hand”. Every time we improve the code generation engine in TX DWA the improvements are just a deployment away, giving you a better data warehouse solution with no extra work.
Multiple Environment Deployment
As the BI backend has become a mission critical asset, it is often needed to have separate environments for development and test, prior to implementing additions and modifications into the live environment. Common scenarios are development-test-live and development-test-QA-live.
With the Multiple Environment Deployment feature, you are offered a configuration approach to ease the migration progress across as many environments as you require. Projects are always transferred as a whole, thus you will never again need to worry about forgetting to transfer or change individual tables or packages. All transfers are version controlled and sequence is enforced to prevent unintended transfers.
TX DWA keeps track of changes to your project with version control, also known as revision control, and enables you to work with your project with peace of mind, since you can always go back to a previous version of your project if needed. A project is defined as the collection of objects such as tables, dimensions and cubes but also includes settings for source and destination connections.
Apart from the ability to restore the project to an earlier point in time, version control serves to document the history of the project. The initial set of objects will be assigned version 1 on the first save of the project. Every subsequent save will be assigned an incremental version number 2, 3, 4 and so on. Each version uniquely identifies the state of the objects as they were at that point in time.
A version also identifies the person that made the changes, a timestamp identifying when the changes were made and optionally a description of the changes that were made. A version of the project is generated both when a project is saved explicitly and when one or more objects are deployed onto SQL Server. The later means that a restore point is automatically generated every time an object such as a table, dimension or cube is created, modified or deleted on SQL Server.
TX DWA supports multiple concurrent developers, effectively allowing true team development. In TX DWA, it’s is possible to lock projects at object level, such as a single table or dimension. Objects can still be locked at a higher level such as an entire data warehouse or even the entire project, for major changes. This flexibility supports different flavors of collaboration between developers.
When working in team development mode, work items are available as a check-in/check-out mechanism to keep track of work in progress. Work items does not enforce an exclusive lock, but ensures visibility about work in progress across concurrent developers, aiding to prevent conflicts. Similar to other development collaboration platforms, Team Development is designed to support multiple developers working concurrently on separate objects within the same project.
Team Development does not guarantee that conflicting changes cannot be made, but it aids at preventing conflicts during high visibility of work in progress. If a conflicting change has been made, the version control capabilities of TX DWA allow you to reopen a previous version of the project.
With SQL Snippets, TX DWA makes it easy to reuse bits of SQL code in transformations. SQL Snippets do not break when you rename objects, are easy to apply, and enables you to edit code for many fields in one place. SQL Snippets are parameterized SQL code with strongly typed SQL transformations. As a result, when a table or fieldname is changed, the transformations that use them are also changed.
When you have created a SQL Snippet, you can use it in any project in the project repository. The snippet can also be exported and imported into other project repositories. You can add your SQL Snippets to all appropriate fields in the project. You can always see an overview of where a particular SQL Snippet is used, and you can update SQL Snippets as required. You can apply SQLSnippets to transformations, views, stored procedures, user defined functions, and script actions.
While we aim to minimize the amount of code you need to write to get a data warehouse up and running, we acknowledge that a complete data warehouse solution will often include some “hand-written” code. To make it easier to integrate this code in TX DWA, the platform allows you to customize the code that it generates in your favorite IDE. You can customize the SSIS package used for data transfer, the transformation script and data cleansing procedure. When you are done, the customized code is loaded back into TX DWA, ready to be used in the next execution of the project.
Interested in TimeXtender Software?
Interested in Partnering with TimeXtender?
VP, Partner Development & Sales
Phone: +1 877 572 3477
VP, Partner Development & Sales
Phone: +45 8620 5700
Director, Partner Development & Sales
Phone: +46 701 46 85 98