Tutorial

Tabular Endpoint

  • 31 March 2023
  • 0 replies
  • 684 views

Userlevel 6
Badge +5

This article describes how to add a Tabular Endpoint to a semantic model instance. On deployment, the model is created on the SSAS Tabular server. To get data in the model, you need to execute the model as well.

In the TimeXtender Portal navigate to Data Estate > Instances, click Add Instance> Add semantic model instance. Select Tabular Endpoint from the Add endpoints list, then click Add an endpoint. Fill out the following fields in the form.

  1. In the Server box, type the name of the Tabular server. The server can be on-premise or in Azure.
  2. In the Database box, type the name of the database.
  3. In the Deployment target list, click the version of SSAS you are targeting. Automatic (default) or Analysis Services Universal are the recommended settings.
  4. In the Compatibility box, click or type the compatibility level you want to use, or leave it blank to use the highest supported by the server.
  5. Under Server login, the following settings are available:
    • Use Windows/Microsoft authentication: Uses the credentials of the user executing the endpoint.
    • Use authentication login: Uses the credentials of a specific user or an App Registration (if the SSAS server is on Azure). This can be useful when your SSAS server is on Azure and the user executing the endpoint has two-factor authentication enabled, which will be triggered by an execution. Enter the user name for the user in the Username box and the corresponding password in the Password box. Prefix the username with 'app:' if it is an App Registration application key.
  6. In the Processing Authentication list, select how the Tabular service will connect to the data warehouse.
    • Click Service account to use the SQL Server Analysis Services service account.
    • Click Windows user to use another user and then enter the user name for the user in the Username box and the corresponding password in the Password box.
  7. Select Process model offline to process the model "behind the scenes" and make the deployment seamless for the users. The offline database will have the endpoint's name prefixed with "Offline_".

Note: if the endpoint uses data from a MDW instance with Snowflake storage follow these additional steps.


0 replies

Be the first to reply!

Reply