A great way to start On-Premise with TimeXtender

This is a standard reference architecture to implement TimeXtender fully in On-Premise.

	1. Create Application Server - Local Server
To serve the TimeXtender application on-premise, we recommend using an Windows environment such as Windows Server sized according to your solution's requirements.
Guide:	Configure an On-Prem Application Server & Storage
Considerations:	This article highlights the Separate Application and Database Servers architecture. In this configuration, the TimeXtender application and services are installed on an "Application" server and the SQL Databases are stored on a separate "Database" server. Once you have chosen your desired configuration and deployed the necessary servers, you must install all the necessary TimeXtender Prerequisites. Configure your server(s) firewall to allow TimeXtender's List of Required Firewall Exceptions. Configure User Accounts & Permissions. Finally, once the user accounts and permissions are in place, you can Download, Install, & Configure TimeXtender.

	2. Create Project Repository - SQL DB
When you save a project, metadata is written to the repository database, and when you open a project, this metadata is read from the project repository and presented in the UI.
Guide:	First Time Set Up of TimeXtender
Considerations:	With credentials to the SQL Server, the Project Repository database may be created directly in the TimeXtender application One Project Repository can contain multiple projects Azure SQL Single DB cannot communicate with other databases, by design.

	3. Create ODX Storage - SQL Server Data Storage
To integrate your siloed data, on-prem SQL DB can store your raw data quickly and easily.
Guide:	Configure the ODX Server
Considerations:	ODX Server Storage database can be created directly in TimeXtender ODX Server Service should be hosted locally on the App Server SQL Server 17 or higher is recommended

	4. Create MDW (and DSA) Storage - Azure SQL DB
SQL DB is a great option for the data warehouse storage, both Modern Data Warehouse (MDW) and Data Staging Area (DSA).
Guide:	Data Warehouses
Considerations:	A data warehouse in TimeXtender is a SQL Server database on premise or in Azure where your data is stored for queries and analysis. Often, a TimeXtender project consists of one data warehouse where you consolidate data from one of more staging databases and a number of data sources. SQL Server 2017 or higher is recommended If using a Data Staging Area (DSA) in your solution, you can use a separate SQL DB as the MDW.

	5. (optional) Create Semantic Model - SQL Server Analysis Services
To serve the Semantic Model in TimeXtender, SQL Server Analysis Services provides reliable, economical. Since there are many ways to connect visualization tools directly to the MDW, this is an optional step.
Guide:	Building Semantic Models
Considerations:	TimeXtender stores semantic models in Analysis Services Tabular model behind the scenes. Each semantic model can be deployed to one or more endpoints.

Reference Architecture with On-Premise SQL Server