Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Latest commit

 

History

History
39 lines (20 loc) · 4.4 KB

UsersGuide-TOC.md

File metadata and controls

39 lines (20 loc) · 4.4 KB

User Guide for Enterprise BI and Reporting

The guide is organized along the sequence of steps that you need to follow to deploy and operationalize the TRI. You can return to specific sections once you have successfully deployed the TRI end-to-end (i.e. after you have completed all the steps until Step 15 below). If the deployment is blocked at any stage, consult the Get Help and Support section for mitigation and workarounds.

  • Step 1 - It is assumed that you have an Azure subscription. If not, obtain a subscription. Then implement these prerequisite steps before deployment

  • Step 2 - Next, set up the deployment, starting from either the GitHub repository, or the Cortana Gallery.

  • Step 3 - Azure is a dynamic environment, and the TRI has several products in its architecture. Please monitor the deployment progress. If the deployment fails or stalls at a given step, you can troubleshoot the deployment.

  • Step 4 - Once the deployment completes with success, you can manage the deployed infrastructure from an Admin console that is provided as part of the TRI.

  • Step 5 - You may also want to monitor the deployed components individually - such as the SQL DW, SSAS, and SSRS servers, the VMs, load balancers, and other components, as part of monitoring the end-to-end system.

  • Step 6 - Once the infrastructure has been deployed in the subscription, the next step is to prepare the infrastructure to ingest your data. This includes optionally removing any demo data and models that are currently in SQL DW and the SSAS servers.

  • Step 7 - The default data generator that is shipped with the TRI is programmed to load demo data files. So you need to modify this script to configure the data ingestion into the SQL Data Warehouse.

  • Step 8 - Once SQL DW is configured for data ingestion, the next step is to configure the SQL Server Analysis Services for generation of analytical tabular models for interactive BI, and the models enabling direct query access for SSRS report generation.

  • Step 9 - Next, configure SQL Server Reporting Services to generate and serve reports.

  • Step 10 - To enable interactive BI against the SSAS cached models, configure Power BI gateway to connect to the SSAS read-only servers through the frontend load balancers, and the Power BI clients for dashboard access.

  • Step 11 - Now that all the data engines are set up, your next step is to do a one-time load of historical data into the SQL DW. Skip this step if you have no historical data, and are starting your BI project from scratch.

  • Step 12 - Follow this with a one time load of all the historical tabular models.

  • Step 13 - Create and/or import dashboards and reports to confirm that your users are able to view the tabular model data through their PowerBI clients, and are able to receive reports.

  • Step 14 - Given the reassurance that the end-to-end pipeline is working for data at rest, you can now confidently set up incremental load of data from your on-premise or cloud based data sources.

  • Step 15 - Incremental data ingestion process is enabled by dynamic ADF pipelines that you may want to monitor and troubleshoot as necessary.

  • Step 16 - If you face any issues with the deployment, consult the frequently asked questions.

  • Step 17 - Get help and support for any of the above steps from the documentation and additional resources provided with the TRI.

  • Step 18 - Finally, for any number of reasons, if you'd like to remove the deployed implementation from your subscription, you can follow these steps for deleting the deployment.