Merge pull request #109735 from Kat-Campise/rebrand_sqldw_v3

rebrand sql dw second 6

Author: Jak-MS

articles/synapse-analytics/sql-data-warehouse/media/sql-data-warehouse-connect-overview/server-connect.PNG

@@ -1,6 +1,6 @@
 ---
-title: Connect to Azure SQL Data Warehouse 
-description: Get connected to Azure SQL Data Warehouse.
+title: Connect to Synapse SQL pool 
+description: Get connected to SQL pool.
 services: synapse-analytics
 author: XiaoyuMSFT 
 manager: craigg
@@ -13,21 +13,23 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Connect to Azure SQL Data Warehouse
-Get connected to Azure SQL Data Warehouse.
+# Connect to Synapse SQL pool
+Get connected to SQL pool.
 
 ## Find your server name
-The server name in the following example is samplesvr.database.windows.net. To find the fully qualified server name:
+The server name in the following example is sqlpoolservername.database.windows.net. To find the fully qualified server name:
 
-1. Go to the [Azure portal][Azure portal].
-2. Click on **SQL data warehouses**.
-3. Click on the data warehouse you want to connect to.
+1. Go to the [Azure portal](https://portal.azure.com).
+2. Click on **Azure Synapse Analytics**.
+3. Click on the SQL pool you want to connect to.
 4. Locate the full server name.
 
     ![Full server name](media/sql-data-warehouse-connect-overview/server-connect.PNG)
 
 ## Supported drivers and connection strings
-Azure SQL Data Warehouse supports [ADO.NET][ADO.NET], [ODBC][ODBC], [PHP][PHP], and [JDBC][JDBC]. To find the latest version and documentation, click on one of the preceding drivers. To automatically generate the connection string for the driver that you are using from the Azure portal, click on the **Show database connection strings** from the preceding example. Following are also some examples of what a connection string looks like for each driver.
+SQL pool supports [ADO.NET](https://msdn.microsoft.com/library/e80y5yhx(v=vs.110).aspx), [ODBC](https://msdn.microsoft.com/library/jj730314.aspx), [PHP](https://msdn.microsoft.com/library/cc296172.aspx?f=255&MSPPError=-2147217396), and [JDBC](https://msdn.microsoft.com/library/mt484311(v=sql.110).aspx). To find the latest version and documentation, click on one of the preceding drivers. 
+
+To automatically generate the connection string for the driver that you are using from the Azure portal, click on the **Show database connection strings** from the preceding example. Following are also some examples of what a connection string looks like for each driver.
 
 > [!NOTE]
 > Consider setting the connection timeout to 300 seconds to allow your connection to survive short periods of unavailability.
@@ -55,36 +57,15 @@ jdbc:sqlserver://yourserver.database.windows.net:1433;database=yourdatabase;user
 ```
 
 ## Connection settings
-SQL Data Warehouse standardizes some settings during connection and object creation. These settings cannot be overridden and include:
+SQL pool standardizes some settings during connection and object creation. These settings cannot be overridden and include:
 
 | Database Setting | Value |
 |:--- |:--- |
-| [ANSI_NULLS][ANSI_NULLS] |ON |
-| [QUOTED_IDENTIFIERS][QUOTED_IDENTIFIERS] |ON |
-| [DATEFORMAT][DATEFORMAT] |mdy |
-| [DATEFIRST][DATEFIRST] |7 |
+| [ANSI_NULLS](https://msdn.microsoft.com/library/ms188048.aspx) |ON |
+| [QUOTED_IDENTIFIERS](https://msdn.microsoft.com/library/ms174393.aspx) |ON |
+| [DATEFORMAT](https://msdn.microsoft.com/library/ms189491.aspx) |mdy |
+| [DATEFIRST](https://msdn.microsoft.com/library/ms181598.aspx) |7 |
 
 ## Next steps
-To connect and query with Visual Studio, see [Query with Visual Studio][Query with Visual Studio]. To learn more about authentication options, see [Authentication to Azure SQL Data Warehouse][Authentication to Azure SQL Data Warehouse].
-
-<!--Articles-->
-[Query with Visual Studio]:sql-data-warehouse-query-visual-studio.md
-[Authentication to Azure SQL Data Warehouse]:sql-data-warehouse-authentication.md
-
-<!--MSDN references-->
-[ADO.NET]: https://msdn.microsoft.com/library/e80y5yhx(v=vs.110).aspx
-[ODBC]: https://msdn.microsoft.com/library/jj730314.aspx
-[PHP]: https://msdn.microsoft.com/library/cc296172.aspx?f=255&MSPPError=-2147217396
-[JDBC]: https://msdn.microsoft.com/library/mt484311(v=sql.110).aspx
-[ANSI_NULLS]: https://msdn.microsoft.com/library/ms188048.aspx
-[QUOTED_IDENTIFIERS]: https://msdn.microsoft.com/library/ms174393.aspx
-[DATEFORMAT]: https://msdn.microsoft.com/library/ms189491.aspx
-[DATEFIRST]: https://msdn.microsoft.com/library/ms181598.aspx
-
-<!--Other-->
-[Azure portal]: https://portal.azure.com
-
-<!--Image references-->
-[1]: media/sql-data-warehouse-connect-overview/server-connect.PNG
-
+To connect and query with Visual Studio, see [Query with Visual Studio](sql-data-warehouse-query-visual-studio.md). To learn more about authentication options, see [Authentication to Azure Synapse Analytics](sql-data-warehouse-authentication.md).
 

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-connect-overview.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
+Included in this article are 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-dynamic-sql.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 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's 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.
+Take note of the CROSS JOIN of the two derived tables since 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. The results are stored 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).

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

@@ -1,6 +1,6 @@
 ---
 title: Using labels to instrument queries
-description: Tips for using labels to instrument queries in Azure SQL Data Warehouse for developing solutions.
+description: Tips for using labels to instrument queries in Synapse SQL pool for developing solutions.
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg
@@ -13,12 +13,12 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Using labels to instrument queries in Azure SQL Data Warehouse
-Tips for using labels to instrument queries in Azure SQL Data Warehouse for developing solutions.
+# Using labels to instrument queries in Synapse SQL pool
+Included in this article are tips for developing solutions using labels to instrument queries in SQL pool.
 
 
 ## What are labels?
-SQL Data Warehouse supports a concept called query labels. Before going into any depth, let's look at an example:
+SQL pool supports a concept called query labels. Before going into any depth, let's look at an example:
 
 ```sql
 SELECT *
@@ -27,11 +27,13 @@ OPTION (LABEL = 'My Query Label')
 ;
 ```
 
-The last line tags the string 'My Query Label' to the query. This tag is particularly helpful since the label is query-able through the DMVs. Querying for labels provides a mechanism for locating problem queries and helping to identify progress through an ELT run.
+The last line tags the string 'My Query Label' to the query. This tag is helpful because the label is query-able through the DMVs. 
 
-A good naming convention really helps. For example, starting the label with PROJECT, PROCEDURE, STATEMENT, or COMMENT helps to uniquely identify the query among all the code in source control.
+Querying for labels provides a mechanism for locating problem queries and helping to identify progress through an ELT run.
 
-The following query uses a dynamic management view to search by label.
+A good naming convention really helps. For example, starting the label with PROJECT, PROCEDURE, STATEMENT, or COMMENT uniquely identifies the query among all the code in source control.
+
+The following query uses a dynamic management view to search by label:
 
 ```sql
 SELECT  *

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

@@ -1,6 +1,6 @@
 ---
 title: Using T-SQL loops
-description: Tips for using T-SQL loops and replacing cursors in Azure SQL Data Warehouse for developing solutions.
+description: Tips for solution development using T-SQL loops and replacing cursors in Synapse SQL pool.
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg
@@ -13,17 +13,21 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Using T-SQL loops in SQL Data Warehouse
-Tips for using T-SQL loops and replacing cursors in Azure SQL Data Warehouse for developing solutions.
+# Using T-SQL loops in Synapse SQL pool
+Included in this article are tips for SQL pool solution development using T-SQL loops and replacing cursors.
 
 ## Purpose of WHILE loops
 
-SQL Data Warehouse supports the [WHILE](/sql/t-sql/language-elements/while-transact-sql) loop for repeatedly executing statement blocks. This WHILE loop continues for as long as the specified conditions are true or until the code specifically terminates the loop using the BREAK keyword. Loops are useful for replacing cursors defined in SQL code. Fortunately, almost all cursors that are written in SQL code are of the fast forward, read-only variety. Therefore, [WHILE] loops are a great alternative for replacing cursors.
+Synapse SQL pool supports the [WHILE](https://docs.microsoft.com/sql/t-sql/language-elements/while-transact-sql?view=sql-server-ver15) loop for repeatedly executing statement blocks. This WHILE loop continues for as long as the specified conditions are true or until the code specifically terminates the loop using the BREAK keyword. 
 
-## Replacing cursors in SQL Data Warehouse
-However, before diving in head first you should ask yourself the following question: "Could this cursor be rewritten to use set-based operations?." In many cases, the answer is yes and is often the best approach. A set-based operation often performs faster than an iterative, row by row approach.
+Loops are useful for replacing cursors defined in SQL code. Fortunately, almost all cursors that are written in SQL code are of the fast forward, read-only variety. So, WHILE loops are a great alternative for replacing cursors.
 
-Fast forward read-only cursors can be easily replaced with a looping construct. The following is a simple example. This code example updates the statistics for every table in the database. By iterating over the tables in the loop, each command executes in sequence.
+## Replacing cursors in Synapse SQL pool
+However, before diving in head first you should ask yourself the following question: "Could this cursor be rewritten to use set-based operations?" 
+
+In many cases, the answer is yes and is frequently the best approach. A set-based operation often performs faster than an iterative, row by row approach.
+
+Fast forward read-only cursors can be easily replaced with a looping construct. The following example is a simple one. This code example updates the statistics for every table in the database. By iterating over the tables in the loop, each command executes in sequence.
 
 First, create a temporary table containing a unique row number used to identify the individual statements: