Skip to content

Commit cf0882a

Browse files
authored
Merge pull request #106184 from Minewiskan/aas-autoscale
Aas autoscale
2 parents 053af73 + a74f725 commit cf0882a

File tree

3 files changed

+12
-5
lines changed

3 files changed

+12
-5
lines changed

articles/analysis-services/analysis-services-logging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.reviewer: minewiskan
1111
---
1212
# Setup diagnostic logging
1313

14-
An important part of any Analysis Services solution is monitoring how your servers are performing. With [Azure resource diagnostic logs](../azure-monitor/platform/platform-logs-overview.md), you can monitor and send logs to [Azure Storage](https://azure.microsoft.com/services/storage/), stream them to [Azure Event Hubs](https://azure.microsoft.com/services/event-hubs/), and export them to [Azure Monitor logs](../azure-monitor/azure-monitor-log-hub.md).
14+
An important part of any Analysis Services solution is monitoring how your servers are performing. With [Azure resource logs](../azure-monitor/platform/platform-logs-overview.md), you can monitor and send logs to [Azure Storage](https://azure.microsoft.com/services/storage/), stream them to [Azure Event Hubs](https://azure.microsoft.com/services/event-hubs/), and export them to [Azure Monitor logs](../azure-monitor/azure-monitor-log-hub.md).
1515

1616
![Diagnostic logging to Storage, Event Hubs, or Azure Monitor logs](./media/analysis-services-logging/aas-logging-overview.png)
1717

articles/analysis-services/analysis-services-samples.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ The [Analysis Services](https://github.com/Microsoft/Analysis-Services) reposito
2121

2222
[Adventure Works for Analysis Services](https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks-analysis-services) on GitHub is the most commonly used sample tabular model project. You can download a VS project or a completed sample tabular model database.
2323

24+
## Sample database on Azure
25+
26+
Azure Synapse Analytics (SQL Data Warehouse) provides a sample AdventureWorksDW database that can be included in a provisioned resource. To learn more, see [Quickstart: Create and query an Azure Synapse Analytics SQL pool](/azure/sql-data-warehouse/create-data-warehouse-portal).
2427

2528
## Sample databases on GitHub
2629

articles/analysis-services/analysis-services-scale-out.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Replicate Azure Analysis Services servers with scale-out. Client qu
44
author: minewiskan
55
ms.service: azure-analysis-services
66
ms.topic: conceptual
7-
ms.date: 01/16/2020
7+
ms.date: 03/02/2020
88
ms.author: owend
99
ms.reviewer: minewiskan
1010

@@ -69,19 +69,23 @@ For maximum performance for both processing and query operations, you can choose
6969

7070
## Monitor QPU usage
7171

72-
To determine if scale-out for your server is necessary, monitor your server in Azure portal by using Metrics. If your QPU regularly maxes out, it means the number of queries against your models is exceeding the QPU limit for your plan. The Query pool job queue length metric also increases when the number of queries in the query thread pool queue exceeds available QPU.
72+
To determine if scale-out for your server is necessary, [monitor your server](analysis-services-monitor.md) in Azure portal by using Metrics. If your QPU regularly maxes out, it means the number of queries against your models is exceeding the QPU limit for your plan. The Query pool job queue length metric also increases when the number of queries in the query thread pool queue exceeds available QPU.
7373

7474
Another good metric to watch is average QPU by ServerResourceType. This metric compares average QPU for the primary server with the query pool.
7575

7676
![Query scale out metrics](media/analysis-services-scale-out/aas-scale-out-monitor.png)
7777

78-
### To configure QPU by ServerResourceType
78+
**To configure QPU by ServerResourceType**
79+
7980
1. In a Metrics line chart, click **Add metric**.
8081
2. In **RESOURCE**, select your server, then in **METRIC NAMESPACE**, select **Analysis Services standard metrics**, then in **METRIC**, select **QPU**, and then in **AGGREGATION**, select **Avg**.
8182
3. Click **Apply Splitting**.
8283
4. In **VALUES**, select **ServerResourceType**.
8384

84-
To learn more, see [Monitor server metrics](analysis-services-monitor.md).
85+
### Detailed diagnostic logging
86+
87+
Use Azure Monitor Logs for more detailed diagnostics of scaled out server resources. With logs, you can use Log Analytics queries to break out QPU and memory by server and replica. To learn more, see example queries in [Analysis Services diagnostics logging](analysis-services-logging.md#example-queries).
88+
8589

8690
## Configure scale-out
8791

0 commit comments

Comments
 (0)