Merge pull request #115420 from Kat-Campise/sql_analytics_naming2

GitHubber17 · web-flow · commit d35a4f011ff6 · 2020-05-15T13:23:48.000-07:00
SQL analytics edits 2
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-concept-resource-utilization-query-activity.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-concept-resource-utilization-query-activity.md
@@ -15,11 +15,11 @@ ms.custom: azure-synapse
 
 # Monitoring resource utilization and query activity in Azure Synapse Analytics
 
-Azure Synapse Analytics provides a rich monitoring experience within the Azure portal to surface insights regarding your data warehouse workload. The Azure portal is the recommended tool when monitoring your data warehouse as it provides configurable retention periods, alerts, recommendations, and customizable charts and dashboards for metrics and logs. The portal also enables you to integrate with other Azure monitoring services such as Azure Monitor (logs) with Log analytics to provide a holistic monitoring experience for not only your data warehouse but also your entire Azure analytics platform for an integrated monitoring experience. This documentation describes what monitoring capabilities are available to optimize and manage your analytics platform with SQL Analytics.
+Azure Synapse Analytics provides a rich monitoring experience within the Azure portal to surface insights regarding your data warehouse workload. The Azure portal is the recommended tool when monitoring your data warehouse as it provides configurable retention periods, alerts, recommendations, and customizable charts and dashboards for metrics and logs. The portal also enables you to integrate with other Azure monitoring services such as Azure Monitor (logs) with Log analytics to provide a holistic monitoring experience for not only your data warehouse but also your entire Azure analytics platform for an integrated monitoring experience. This documentation describes what monitoring capabilities are available to optimize and manage your analytics platform with Synapse SQL.
 
 ## Resource utilization
 
-The following metrics are available in the Azure portal for SQL Analytics. These metrics are surfaced through [Azure Monitor](../../azure-monitor/platform/data-collection.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#metrics).
+The following metrics are available in the Azure portal for Synapse SQL. These metrics are surfaced through [Azure Monitor](../../azure-monitor/platform/data-collection.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#metrics).
 
 | Metric Name             | Description                                                  | Aggregation Type |
 | ----------------------- | ------------------------------------------------------------ | ---------------- |
@@ -49,13 +49,13 @@ Things to consider when viewing metrics and setting alerts:
 
 ## Query activity
 
-For a programmatic experience when monitoring SQL Analytics via T-SQL, the service provides a set of Dynamic Management Views (DMVs). These views are useful when actively troubleshooting and identifying performance bottlenecks with your workload.
+For a programmatic experience when monitoring Synapse SQL via T-SQL, the service provides a set of Dynamic Management Views (DMVs). These views are useful when actively troubleshooting and identifying performance bottlenecks with your workload.
 
 To view the list of DMVs that apply to Synapse SQL, refer to this [documentation](../sql/reference-tsql-system-views.md#sql-pool-dynamic-management-views-dmvs). 
 
 ## Metrics and diagnostics logging 
 
-Both metrics and logs can be exported to Azure Monitor, specifically the [Azure Monitor logs](../../azure-monitor/log-query/log-query-overview.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json) component and can be programmatically accessed through [log queries](../../azure-monitor/log-query/get-started-portal.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json). The log latency for SQL Analytics is about 10-15 minutes. For more details on the factors impacting latency, visit the following documentation.
+Both metrics and logs can be exported to Azure Monitor, specifically the [Azure Monitor logs](../../azure-monitor/log-query/log-query-overview.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json) component and can be programmatically accessed through [log queries](../../azure-monitor/log-query/get-started-portal.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json). The log latency for Synapse SQL is about 10-15 minutes. For more details on the factors impacting latency, visit the following documentation.
 
 ## Next steps
 
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-load-from-azure-data-lake-store.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-load-from-azure-data-lake-store.md
@@ -13,7 +13,7 @@ ms.reviewer: igorstan
 ms.custom: azure-synapse
 ---
 
-# Load data from Azure Data Lake Storage for SQL Analytics
+# Load data from Azure Data Lake Storage for Synapse SQL
 
 This guide outlines how to use PolyBase external tables to load data from Azure Data Lake Storage. Although you can run adhoc queries on data stored in Data Lake Storage, we recommend importing the data for best performance.
 
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-integrate.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-integrate.md
@@ -13,16 +13,16 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Integrate other services with a SQL Analytics data warehouse
+# Integrate other services with a Synapse SQL pool (data warehouse)
 
-The SQL Analytics capability within Azure Synapse Analytics enables users to integrate with many of the other services in Azure. Using SQL Analytics, you can create a data warehouse via its SQL pool resource, which can then utilize several additional services, some of which include:
+The SQL pool capability within Azure Synapse Analytics enables users to integrate with many of the other services in Azure. Using Synapse SQL, you can create a data warehouse via its SQL pool resource, which can then utilize several additional services, some of which include:
 
 * Power BI
 * Azure Data Factory
 * Azure Machine Learning
 * Azure Stream Analytics
 
-For more information regarding integration services across Azure, review the [Integration partners](sql-data-warehouse-partner-data-integration.md)article.
+For more information about integration services across Azure, review the [Integration partners](sql-data-warehouse-partner-data-integration.md)article.
 
 ## Power BI
 
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-temporary.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-temporary.md
@@ -24,7 +24,7 @@ Temporary tables are only visible to the session in which they were created and
 
 Temporary tables offer a performance benefit because their results are written to local rather than remote storage.
 
-Temporary tables are useful when processing data, especially during transformation where the intermediate results are transient. With SQL Analytics, temporary tables exist at the session level.  They're only visible to the session in which they were created. As such, they're automatically dropped when that session logs off. 
+Temporary tables are useful when processing data, especially during transformation where the intermediate results are transient. With SQL pool, temporary tables exist at the session level.  They're only visible to the session in which they were created. As such, they're automatically dropped when that session logs off. 
 
 ## Temporary tables in SQL pool
 
@@ -228,5 +228,5 @@ Also, views can't be created on temporary tables.  Temporary tables can only be
 
 ## Next steps
 
-To learn more about developing tables, see the [Designing tables using the SQL Analytics resources](sql-data-warehouse-tables-overview.md) article.
+To learn more about developing tables, see the [Designing tables using the Synapse SQL resources](sql-data-warehouse-tables-overview.md) article.
 
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot-connectivity.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot-connectivity.md
@@ -13,40 +13,40 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019, azure-synapse
 ---
 
-# Troubleshooting connectivity issues
+# Troubleshooting connectivity issues in Synapse SQL pool
 
-This article lists common troubleshooting techniques around connecting to your SQL Analytics database.
+This article lists common troubleshooting techniques around connecting to your SQL pool database.
 
 ## Check service availability
 
-Check to see if the service is available. In the Azure portal, go to the Synapse SQL pool you're trying to connect. In the left TOC panel, click on **Diagnose and solve problems**.
+Check to see if the service is available. In the Azure portal, go to the  SQL pool you're trying to connect. In the left TOC panel, click on **Diagnose and solve problems**.
 
 ![Select Resource health](./media/sql-data-warehouse-troubleshoot-connectivity/diagnostics-link.png)
 
-The status of your Synapse SQL pool will be shown here. If the service isn't showing as **Available**, check further steps.
+The status of your SQL pool will be shown here. If the service isn't showing as **Available**, check further steps.
 
 ![Service Available](./media/sql-data-warehouse-troubleshoot-connectivity/resource-health.png)
 
-If your Resource health shows that your Synapse SQL pool instance is paused or scaling, follow the guidance to resume your instance.
+If your Resource health shows that your SQL pool instance is paused or scaling, follow the guidance to resume your instance.
 
 ![Service Paused](./media/sql-data-warehouse-troubleshoot-connectivity/resource-health-pausing.png)
 Additional information about Resource Health can be found here.
 
 ## Check for paused or scaling operation
 
-Check the portal to see if your Synapse SQL pool instance is paused or scaling.
+Check the portal to see if your SQL pool instance is paused or scaling.
 
 ![Service Paused](./media/sql-data-warehouse-troubleshoot-connectivity/overview-paused.png)
 
-If you see that your service is paused or scaling, check to see it isn't during your maintenance schedule. On the portal for your Synapse SQL pool *Overview*, you'll see the elected maintenance schedule.
+If you see that your service is paused or scaling, check to see it isn't during your maintenance schedule. On the portal for your SQL pool *Overview*, you'll see the elected maintenance schedule.
 
 ![Overview Maintenance Schedule](./media/sql-data-warehouse-troubleshoot-connectivity/overview-maintance-schedule.png)
 
-Otherwise, check with your IT administrator to verify that this maintenance isn't a scheduled event. To resume the SQL Analytics instance, follow [these steps](pause-and-resume-compute-portal.md).
+Otherwise, check with your IT administrator to verify that this maintenance isn't a scheduled event. To resume the SQL pool instance, follow [these steps](pause-and-resume-compute-portal.md).
 
 ## Check your firewall settings
 
-SQL Analytics database communicates over port 1433.   If you're trying to connect from within a corporate network, outbound traffic over port 1433 might not be allowed by your network's firewall. In that case, you can't connect to your Azure SQL Database server unless your IT department opens port 1433. Additional information on firewall configurations can be found [here](../../sql-database/sql-database-firewall-configure.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#create-and-manage-ip-firewall-rules).
+The SQL pool database communicates over port 1433.  If you're trying to connect from within a corporate network, outbound traffic over port 1433 might not be allowed by your network's firewall. In that case, you can't connect to your Azure SQL Database server unless your IT department opens port 1433. Additional information on firewall configurations can be found [here](../../sql-database/sql-database-firewall-configure.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#create-and-manage-ip-firewall-rules).
 
 ## Check your VNet/Service Endpoint settings
 
@@ -56,7 +56,7 @@ If you're receiving Errors 40914 and 40615, see [error description and resolutio
 
 ### Software
 
-Check to make sure you're using the latest tools to connect to your Synapse SQL pool:
+Check to make sure you're using the latest tools to connect to your  SQL pool:
 
 - SSMS
 - Azure Data Studio
@@ -101,7 +101,7 @@ jdbc:sqlserver://yourserver.database.windows.net:1433;database=yourdatabase;user
 
 ## Intermittent connection issues
 
-Check to see if you're experiencing heavy load on the server with a high number of queued requests. You may need to scale up your Synapse SQL pool for additional resources.
+Check to see if you're experiencing heavy load on the server with a high number of queued requests. You may need to scale up your  SQL pool for additional resources.
 
 ## Common error messages
 
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot.md
@@ -1,6 +1,6 @@
 ---
-title: Troubleshooting
-description: Troubleshooting Azure Synapse Analytics.
+title: Troubleshooting  
+description: Troubleshooting Synapse SQL in Azure Synapse Analytics.
 services: synapse-analytics
 author: kevinvngo
 manager: craigg
@@ -13,9 +13,9 @@ ms.reviewer: jrasnick
 ms.custom: azure-synapse
 ---
 
-# Troubleshooting SQL Analytics in Azure Synapse
+# Troubleshooting Synapse SQL in Azure Synapse Analytics
 
-This article lists common troubleshooting question.
+This article lists common troubleshooting issues in Synapse SQL.
 
 ## Connecting
 
diff --git a/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-workload-management.md b/articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-workload-management.md
@@ -15,7 +15,7 @@ ms.custom: azure-synapse
 
 # What is workload management?
 
-Running mixed workloads can pose resource challenges on busy systems.  Solution Architects seek ways to separate classic data warehousing activities (such as loading, transforming and querying data) to ensure that enough resources exist to hit SLAs.  
+Running mixed workloads can pose resource challenges on busy systems.  Solution Architects seek ways to separate classic data warehousing activities (such as loading, transforming, and querying data) to ensure that enough resources exist to hit SLAs.  
 
 Physical server isolation can lead to pockets of infrastructure that are underutilized, overbooked or in a state where caches are constantly being primed with hardware starting and stopping.  A successful workload management scheme effectively manages resources, ensures highly efficient resource utilization, and maximizes return on investment (ROI).
 
@@ -33,13 +33,13 @@ The performance capacity of a data warehouse is determined by the [data warehous
 
 ## Workload management concepts
 
-In the past, for SQL Analytics in Azure Synapse you managed the query performance through [resource classes](resource-classes-for-workload-management.md).  Resource classes allowed for assigning memory to a query based on role membership.  The primary challenge with resources classes is that, once configured, there was no governance or ability to control the workload.  
+In the past, for Synapse SQL in Azure Synapse you managed the query performance through [resource classes](resource-classes-for-workload-management.md).  Resource classes allowed for assigning memory to a query based on role membership.  The primary challenge with resources classes is that, once configured, there was no governance or ability to control the workload.  
 
 For example, granting an ad-hoc user role membership to smallrc allowed that user to consume 100% of the memory on the system.  With resource classes, there is no way to reserve and ensure resources are available for critical workloads.
 
-Synapse SQL pool workload management in Azure Synapse consists of three high-level concepts: [Workload Classification](sql-data-warehouse-workload-classification.md), [Workload Importance](sql-data-warehouse-workload-importance.md) and [Workload Isolation](sql-data-warehouse-workload-isolation.md).  These capabilities give you more control over how your workload utilizes system resources.
+Synapse SQL pool workload management in Azure Synapse consists of three high-level concepts: [Workload Classification](sql-data-warehouse-workload-classification.md), [Workload Importance](sql-data-warehouse-workload-importance.md), and [Workload Isolation](sql-data-warehouse-workload-isolation.md).  These capabilities give you more control over how your workload utilizes system resources.
 
-Workload classification is the concept of assigning a request to a workload group and setting importance levels.  Historically, this assignment was done via role membership using [sp_addrolemember](resource-classes-for-workload-management.md#change-a-users-resource-class).  This can now be done via the [CREATE WORKLOAD CLASSIFER](/sql/t-sql/statements/create-workload-classifier-transact-sql?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest).  The classification capability provides a richer set of options such as label, session, and time to classify requests.
+Workload classification is the concept of assigning a request to a workload group and setting importance levels.  Historically, this assignment was done via role membership using [sp_addrolemember](resource-classes-for-workload-management.md#change-a-users-resource-class).  This action can now be done via the [CREATE WORKLOAD CLASSIFER](/sql/t-sql/statements/create-workload-classifier-transact-sql?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest).  The classification capability provides a richer set of options such as label, session, and time to classify requests.
 
 Workload importance influences the order in which a request gets access to resources.  On a busy system, a request with higher importance has first access to resources.  Importance can also ensure ordered access to locks.
 
