dynamic and group by

Author: Kat-Campise

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-dynamic-sql.md

@@ -1,6 +1,6 @@
 ---
 title: Using dynamic SQL 
-description: Tips for using dynamic SQL in Azure SQL Data Warehouse for developing solutions.
+description: Tips for development solutions using dynamic SQL in Synapse SQL pool.
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg
@@ -13,12 +13,16 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Dynamic SQL in SQL Data Warehouse
-Tips for using dynamic SQL in Azure SQL Data Warehouse for developing solutions.
+# Dynamic SQL in Synapse SQL pool
+Tips for development solutions using dynamic SQL in SQL pool.
 
 ## Dynamic SQL Example
 
-When developing application code for SQL Data Warehouse, you may need to use dynamic sql to help deliver flexible, generic, and modular solutions. SQL Data Warehouse does not support blob data types at this time. Not supporting blob data types might limit the size of your strings since blob data types include both varchar(max) and nvarchar(max) types. If you have used these types in your application code to build large strings, you need to break the code into chunks and use the EXEC statement instead.
+When developing application code for SQL pool, you may need to use Dynamic SQL to help deliver flexible, generic, and modular solutions. SQL pool doesn't support blob data types at this time. 
+
+Not supporting blob data types might limit the size of your strings since blob data types include both varchar(max) and nvarchar(max) types. 
+
+If you've used these types in your application code to build large strings, you need to break the code into chunks and use the EXEC statement instead.
 
 A simple example:
 
@@ -33,7 +37,7 @@ EXEC( @sql_fragment1 + @sql_fragment2 + @sql_fragment3);
 If the string is short, you can use [sp_executesql](/sql/relational-databases/system-stored-procedures/sp-executesql-transact-sql) as normal.
 
 > [!NOTE]
-> Statements executed as dynamic SQL will still be subject to all TSQL validation rules.
+> Statements executed as dynamic SQL will still be subject to all T-SQL validation rules.
 > 
 > 
 

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-group-by-options.md

@@ -1,6 +1,6 @@
 ---
 title: Using group by options 
-description: Tips for implementing group by options in Azure SQL Data Warehouse for developing solutions.
+description: Tips for implementing group by options in Synapse SQL pool.
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg
@@ -13,21 +13,21 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Group by options in SQL Data Warehouse
-Tips for implementing group by options in Azure SQL Data Warehouse for developing solutions.
+# Group by options in Synapse SQL pool
 
-## What does GROUP BY do?
+In this article, you'll find tips for implementing group by options in SQL pool.
 
-The [GROUP BY](/sql/t-sql/queries/select-group-by-transact-sql) T-SQL clause aggregates data to a summary set of rows. GROUP BY has some options that SQL Data Warehouse does not support. These options have workarounds.
+## What does GROUP BY do?
 
-These options are
+The [GROUP BY](/sql/t-sql/queries/select-group-by-transact-sql) T-SQL clause aggregates data to a summary set of rows. GROUP BY has some options that SQL pool doesn't support. These options have workarounds, which are as follows:
 
 * GROUP BY with ROLLUP
 * GROUPING SETS
 * GROUP BY with CUBE
 
 ## Rollup and grouping sets options
-The simplest option here is to use UNION ALL instead to perform the rollup rather than relying on the explicit syntax. The result is exactly the same
+
+The simplest option here is to use UNION ALL instead to perform the rollup rather than relying on the explicit syntax. The result is exactly the same.
 
 The following example using the GROUP BY statement with the ROLLUP option:
 ```sql
@@ -79,11 +79,11 @@ JOIN  dbo.DimSalesTerritory t     ON s.SalesTerritoryKey       = t.SalesTerritor
 To replace GROUPING SETS, the sample principle applies. You only need to create UNION ALL sections for the aggregation levels you want to see.
 
 ## Cube options
-It is possible to create a GROUP BY WITH CUBE using the UNION ALL approach. The problem is that the code can quickly become cumbersome and unwieldy. To mitigate this, you can use this more advanced approach.
+It is possible to create a GROUP BY WITH CUBE using the UNION ALL approach. The problem is that the code can quickly become cumbersome and unwieldy. To mitigate this issue, you can use this more advanced approach.
 
-Let's use the example above.
+Using the previous example, the first step is to define the 'cube' that defines all the levels of aggregation that we want to create. 
 
-The first step is to define the 'cube' that defines all the levels of aggregation that we want to create. It is important to take note of the CROSS JOIN of the two derived tables. This generates all the levels for us. The rest of the code is really there for formatting.
+It is important to take note of the CROSS JOIN of the two derived tables. This generates all the levels for us. The rest of the code is there for formatting:
 
 ```sql
 CREATE TABLE #Cube
@@ -114,7 +114,7 @@ SELECT Cols
 FROM GrpCube;
 ```
 
-The following shows the results of the CTAS:
+The following image shows the results of the CTAS:
 
 ![Group by cube](./media/sql-data-warehouse-develop-group-by-options/sql-data-warehouse-develop-group-by-cube.png)
 
@@ -141,7 +141,7 @@ WITH
 ;
 ```
 
-The third step is to loop over our cube of columns performing the aggregation. The query will run once for every row in the #Cube temporary table and store the results in the #Results temp table
+The third step is to loop over our cube of columns performing the aggregation. The query will run once for every row in the #Cube temporary table and store the results in the #Results temp table:
 
 ```sql
 SET @nbr =(SELECT MAX(Seq) FROM #Cube);
@@ -165,7 +165,7 @@ BEGIN
 END
 ```
 
-Lastly, you can return the results by simply reading from the #Results temporary table
+Lastly, you can return the results by reading from the #Results temporary table:
 
 ```sql
 SELECT *
@@ -174,7 +174,7 @@ ORDER BY 1,2,3
 ;
 ```
 
-By breaking the code up into sections and generating a looping construct, the code becomes more manageable and maintainable.
+By breaking up the code into sections and generating a looping construct, the code becomes more manageable and maintainable.
 
 ## Next steps
 For more development tips, see [development overview](sql-data-warehouse-overview-develop.md).