You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/analysis-services/analysis-services-database-users.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ When adding a **service principal** use `app:appid@tenantid`.
53
53
54
54
8. In **Add External Member**, enter users or groups in your tenant Azure AD by email address. After you click OK and close Role Manager, roles and role members appear in Tabular Model Explorer.
55
55
56
-
56
+
57
57
58
58
9. Deploy to your Azure Analysis Services server.
59
59
@@ -76,7 +76,7 @@ To add roles and users to a deployed model database, you must be connected to th
76
76
77
77
4. Click **Membership**, then enter a user or group in your tenant Azure AD by email address.
5. If the role you are creating has Read permission, you can add row filters by using a DAX formula. Click **Row Filters**, select a table, and then type a DAX formula in the **DAX Filter** field.
Copy file name to clipboardExpand all lines: articles/analysis-services/analysis-services-datasource.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,15 +92,15 @@ When using the Table Import Wizard in Visual Studio, connections to any data sou
92
92
93
93
To enable provider data sources, in Visual Studio, click **Tools** > **Options** > **Analysis Services Tabular** > **Data Import**, select **Enable legacy data sources**.
94
94
95
-
95
+
96
96
97
97
With legacy data sources enabled, in **Tabular Model Explorer**, right-click **Data Sources** > **Import From Data Source (Legacy)**.
98
98
99
-
99
+
100
100
101
101
Just like with tabular 1200 model projects, use **Table Import Wizard** to connect to a data source. On the connect page, click **Advanced**. Specify data provider and other connection settings in **Set Advanced Properties**.
102
102
103
-
103
+
104
104
105
105
## Impersonation
106
106
In some cases, it may be necessary to specify a different impersonation account. Impersonation account can be specified in Visual Studio or SQL Server Management Studio (SSMS).
Copy file name to clipboardExpand all lines: articles/analysis-services/analysis-services-deploy.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,20 +30,20 @@ To get started, you need:
30
30
31
31
In **Azure portal** > server > **Overview** > **Server name**, copy the server name.
32
32
33
-
33
+
34
34
35
35
## To deploy from Visual Studio
36
36
37
37
1. In Visual Studio > **Solution Explorer**, right-click the project > **Properties**. Then in **Deployment** > **Server** paste the server name.
38
38
39
-
39
+
40
40
2. In **Solution Explorer**, right-click **Properties**, then click **Deploy**. You may be prompted to sign in to Azure.
41
41
42
-
42
+
43
43
44
44
Deployment status appears in both the Output window and in Deploy.
2. Select a location, accept the terms, and then click **Install**.
59
59
60
-
60
+
61
61
62
62
3. Sign in to Azure. The account must be in your tenant's Azure Active Directory. This account is used for the gateway administrator. Azure B2B (guest) accounts are not supported when installing and registering the gateway.
63
63
64
-
64
+
65
65
66
66
> [!NOTE]
67
67
> If you sign in with a domain account, it's mapped to your organizational account in Azure AD. Your organizational account is used as the gateway administrator.
@@ -79,7 +79,7 @@ In order to create a gateway resource in Azure, you must register the local inst
79
79
> [!IMPORTANT]
80
80
> Save your recovery key in a safe place. The recovery key is required in-order to takeover, migrate, or restore a gateway.
Copy file name to clipboardExpand all lines: articles/analysis-services/analysis-services-logging.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ The Metrics category logs the same [Server metrics](analysis-services-monitor.md
70
70
71
71
1. In [Azure portal](https://portal.azure.com) > server, click **Diagnostic settings** in the left navigation, and then click **Turn on diagnostics**.
72
72
73
-
73
+
74
74
75
75
2. In **Diagnostic settings**, specify the following options:
76
76
@@ -152,7 +152,7 @@ Metrics and server events are integrated with xEvents in your Log Analytics work
152
152
153
153
To view your diagnostic data, in Log Analytics workspace, open **Logs** from the left menu.
154
154
155
-
155
+
156
156
157
157
In the query builder, expand **LogManagement** > **AzureDiagnostics**. AzureDiagnostics includes Engine and Service events. Notice a query is created on-the-fly. The EventClass\_s field contains xEvent names, which may look familiar if you've used xEvents for on-premises logging. Click **EventClass\_s** or one of the event names and Log Analytics workspace continues constructing a query. Be sure to save your queries to reuse later.
0 commit comments