20240729 edit pass

Author: WilliamDAssafMSFT

articles/synapse-analytics/sql-data-warehouse/resource-classes-for-workload-management.md

@@ -88,13 +88,13 @@ Resource classes are designed to improve performance for data management and man
 
 These operations are governed by resource classes:
 
-- INSERT-SELECT, UPDATE, DELETE
-- SELECT (when querying user tables)
-- ALTER INDEX - REBUILD or REORGANIZE
-- ALTER TABLE REBUILD
-- CREATE INDEX
-- CREATE CLUSTERED COLUMNSTORE INDEX
-- CREATE TABLE AS SELECT (CTAS)
+- `INSERT`-`SELECT`, `UPDATE`, `DELETE`
+- `SELECT` (when querying user tables)
+- `ALTER INDEX` - `REBUILD` or `REORGANIZE`
+- `ALTER TABLE REBUILD`
+- `CREATE INDEX`
+- `CREATE CLUSTERED COLUMNSTORE INDEX`
+- `CREATE TABLE AS SELECT` (CTAS)
 - Data loading
 - Data movement operations conducted by the Data Movement Service (DMS)
 
@@ -107,21 +107,21 @@ Some queries always run in the smallrc resource class even though the user is a
 
 The following statements are exempt from resource classes and always run in smallrc:
 
-- CREATE or DROP TABLE
-- ALTER TABLE ... SWITCH, SPLIT, or MERGE PARTITION
-- ALTER INDEX DISABLE
-- DROP INDEX
-- CREATE, UPDATE, or DROP STATISTICS
-- TRUNCATE TABLE
-- ALTER AUTHORIZATION
-- CREATE LOGIN
-- CREATE, ALTER, or DROP USER
-- CREATE, ALTER, or DROP PROCEDURE
-- CREATE or DROP VIEW
-- INSERT VALUES
-- SELECT from system views and DMVs
-- EXPLAIN
-- DBCC
+- `CREATE` or `DROP TABLE`
+- `ALTER TABLE ... SWITCH`, `SPLIT`, or `MERGE PARTITION`
+- `ALTER INDEX DISABLE`
+- `DROP INDEX`
+- `CREATE`, `UPDATE`, or `DROP STATISTICS`
+- `TRUNCATE TABLE`
+- `ALTER AUTHORIZATION`
+- `CREATE LOGIN`
+- `CREATE`, `ALTER`, or `DROP USER`
+- `CREATE`, `ALTER`, or `DROP PROCEDURE`
+- `CREATE` or `DROP VIEW`
+- `INSERT VALUES`
+- `SELECT` from system views and DMVs
+- `EXPLAIN`
+- `DBCC`
 
 <!--
 Removed as these two are not confirmed / supported under Azure Synapse Analytics
@@ -169,7 +169,7 @@ EXEC sp_droprolemember 'largerc', 'loaduser';
 
 Users can be members of multiple resource classes. When a user belongs to more than one resource class:
 
-- Dynamic resource classes take precedence over static resource classes. For example, if a user is a member of both mediumrc(dynamic) and staticrc80 (static), queries run with mediumrc.
+- Dynamic resource classes take precedence over static resource classes. For example, if a user is a member of both mediumrc (dynamic) and staticrc80 (static), queries run with mediumrc.
 - Larger resource classes take precedence over smaller resource classes. For example, if a user is a member of mediumrc and largerc, queries run with largerc. Likewise, if a user is a member of both staticrc20 and statirc80, queries run with staticrc80 resource allocations.
 
 ## Recommendations
@@ -226,8 +226,8 @@ For examples, see [Usage example](#usage-example).
 >[!NOTE]  
 >If you are not getting output after executing stored procedure with parameters provided, then there could be two cases.
 >
->1. Either DW Parameter contains an invalid SLO value
->2. Or, there is no matching resource class for the CCI operation on the table.
+>- Either DW Parameter contains an invalid SLO value
+>- Or, there is no matching resource class for the CCI operation on the table.
 >
 >For example, at DW100c, the highest memory grant available is 1 GB, and if table schema is wide enough to cross the requirement of 1 GB.
 
@@ -236,9 +236,9 @@ For examples, see [Usage example](#usage-example).
 Syntax:  
 `EXEC dbo.prc_workload_management_by_DWU @DWU VARCHAR(7), @SCHEMA_NAME VARCHAR(128), @TABLE_NAME VARCHAR(128)`
 
-1. @DWU: Either provide a NULL parameter to extract the current DWU from the DW DB or provide any supported DWU in the form of 'DW100c'
-1. @SCHEMA_NAME: Provide a schema name of the table
-1. @TABLE_NAME: Provide a table name of the interest
+- `@DWU`: Either provide a `NULL` parameter to extract the current DWU from the DW DB or provide any supported DWU in the form of 'DW100c'
+- `@SCHEMA_NAME`: Provide a schema name of the table
+- `@TABLE_NAME`: Provide a table name of the interest
 
 Examples executing this stored proc:
 

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-how-to-troubleshoot-missed-classification.md

@@ -139,9 +139,9 @@ Consider a scenario for the Azure Synapse Workspace SQL Admin login, the Azure S
 
 **Recommendation**: These administrative users can't change their default workload group. For more information, see [workload management with resource classes](resource-classes-for-workload-management.md#default-resource-class). It is recommended that critical or performance-sensitive workloads not run as one of these administrative users in the dedicated SQL pool.
 
-The Azure Synapse Workspace SQL Admin login and the Azure Synapse Microsoft Entra admin (user or group member) are specified in the Azure portal, on the **Overview** page of the dedicated SQL pool.
+   The Azure Synapse Workspace SQL Admin login and the Azure Synapse Microsoft Entra admin (user or group member) are specified in the Azure portal, on the **Overview** page of the dedicated SQL pool.
 
-Similarly, the database owner (dbo) and **db_owner** database roles are not allowed to change their default resource class. If a user is either the database owner or added under **db_owner** database role, all queries executed by the user go to smallrc by default. These roles can't be added to a resource class other than smallrc. However, if a user who is part of this role would like to classify their queries to a different workload group, they can use `MEMBERNAME` option in [workload classifier definition](sql-data-warehouse-workload-classification.md).
+   Similarly, the database owner (dbo) and **db_owner** database roles are not allowed to change their default resource class. If a user is either the database owner or added under **db_owner** database role, all queries executed by the user go to smallrc by default. These roles can't be added to a resource class other than smallrc. However, if a user who is part of this role would like to classify their queries to a different workload group, they can use `MEMBERNAME` option in [workload classifier definition](sql-data-warehouse-workload-classification.md).
 
 ### Use workload group precedence for better classification
 
@@ -157,9 +157,9 @@ In scenarios where resource classes are being used it's best to create a dedicat
 1. Dynamic resource class takes precedence over static resource class. For example, if a user is member of mediumrc (dynamic) and staticrc80(static), user queries run with mediumrc.
 1. Bigger resource classes are preferred over smaller resource classes. For example, if a user is member of staticrc20 and staticrc80, then user queries will run with staticrc80.
 
-#### If Workload Management Capabilities are used
+#### If workload management capabilities are used
 
-WLM provides capability to create multiple workload classifiers for same user or workload group. Classifier definition statement has multiple parameters based on which incoming requests are assigned to workloads. These parameters have a **weight** score as shown below and this score determines order of precedence: 
+Workload management (WLM) capabilities provide capability to create multiple workload classifiers for same user or workload group. Classifier definition statement has multiple parameters based on which incoming requests are assigned to workloads. These parameters have a **weight** score as shown below and this score determines order of precedence: 
 
 |**Classifier parameter** |**Weight**   |
 |---------------------|---------|
@@ -186,7 +186,7 @@ CREATE WORKLOAD CLASSIFIER CLASSIFIER-2 WITH
  ,IMPORTANCE     = 'Low')
 ```
 
-Queries submitted by User-1 can be submitted via both classifiers. Query run by User-1 with the 'dimension_loads' label between 6PM and 7AM UTC will be assigned to `wgDashboards` as weight score of WLM_LABEL is higher than START_TIME/END_TIME. The weighting of `CLASSIFIER-1` is 80 (64 for user, plus 16 for WLM_LABEL). The weighting of `CLASSIFIER-2` is 68 (64 for user, 4 for START_TIME/END_TIME). 
+Queries submitted by User-1 can be submitted via both classifiers. Query run by User-1 with the `dimension_loads` label between 6PM and 7AM UTC will be assigned to `wgDashboards` as weight score of `WLM_LABEL` is higher than `START_TIME`/`END_TIME`. The weighting of `CLASSIFIER-1` is 80 (64 for user, plus 16 for `WLM_LABEL`). The weighting of `CLASSIFIER-2` is 68 (64 for user, 4 for `START_TIME`/`END_TIME`). 
 
 For more information on workload classification, see [classification weighting](sql-data-warehouse-workload-classification.md#classification-weighting) and [query labels](../sql/develop-label.md).
 
@@ -296,5 +296,5 @@ If there was a tie in workload groups or classifiers, following precedence takes
 ## Related content 
 
 - For more information on workload classification, see [Workload Classification](sql-data-warehouse-workload-classification.md).
-- For more information on workload importance, see [Workload Importance](sql-data-warehouse-workload-importance.md)
- 
+- For more information on workload importance, see [Workload Importance](sql-data-warehouse-workload-importance.md).
+ 

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-workload-classification.md

@@ -18,15 +18,13 @@ This article explains the workload classification process of assigning a workloa
 
 ## Classification
 
-> [!Video https://www.youtube.com/embed/QcCRBAhoXpM]
-
 Workload management classification allows workload policies to be applied to requests through assigning [resource classes](resource-classes-for-workload-management.md#what-are-resource-classes) and [importance](sql-data-warehouse-workload-importance.md).
 
 While there are many ways to classify data warehousing workloads, the simplest and most common classification is load and query. You load data with insert, update, and delete statements. You query the data using selects. A data warehousing solution will often have a workload policy for load activity, such as assigning a higher resource class with more resources. A different workload policy could apply to queries, such as lower importance compared to load activities.
 
 You can also subclassify your load and query workloads. Subclassification gives you more control of your workloads. For example, query workloads can consist of cube refreshes, dashboard queries or ad hoc queries. You can classify each of these query workloads with different resource classes or importance settings. Load can also benefit from subclassification. Large transformations can be assigned to larger resource classes. Higher importance can be used to ensure key sales data is loader before weather data or a social data feed.
 
-Not all statements are classified as they do not require resources or need importance to influence execution. DBCC commands, BEGIN, COMMIT, and ROLLBACK TRANSACTION statements are not classified.
+Not all statements are classified as they do not require resources or need importance to influence execution. `DBCC` commands, `BEGIN`, `COMMIT`, and `ROLLBACK TRANSACTION` statements are not classified.
 
 ## Classification process