Merge pull request #110034 from Kat-Campise/rebrand_sqldw_v5

rebrand sqldw fourth 6

Author: megvanhuygen

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

@@ -1,6 +1,6 @@
 ---
-title: Resources for developing a data warehouse in Azure Synapse Analytics
-description: Development concepts, design decisions, recommendations and coding techniques for SQL Data Warehouse.
+title: Resources for developing a Synapse SQL pool in Azure Synapse Analytics
+description: Development concepts, design decisions, recommendations, and coding techniques for SQL pool.
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg
@@ -12,11 +12,11 @@ ms.author: xiaoyul
 ms.reviewer: igorstan
 ---
 
-# Design decisions and coding techniques for a data warehouse in Azure Synapse Analytics 
- In this article, you'll find additional resources to help you better understand key design decisions, recommendations, and coding techniques for a data warehouse in Azure Synapse.
+# Design decisions and coding techniques for a Synapse SQL pool in Azure Synapse Analytics 
+ In this article, you'll find additional resources to help you better understand key design decisions, recommendations, and coding techniques for a SQL pool.
 
 ## Key design decisions
-The following articles highlight concepts and design decisions for developing a distributed data warehouse using the SQL Analytics capability in Azure Synapse:
+The following articles highlight concepts and design decisions for developing a distributed SQL pool:
 
 * [connections](sql-data-warehouse-connect-overview.md)
 * [concurrency](resource-classes-for-workload-management.md)
@@ -29,7 +29,7 @@ The following articles highlight concepts and design decisions for developing a
 * [statistics](sql-data-warehouse-tables-statistics.md)
 
 ## Development recommendations and coding techniques
-The following articles feature specific coding techniques, tips, and recommendations for developing a data warehouse with SQL Analytics:
+The following articles feature specific coding techniques, tips, and recommendations for developing a SQL pool:
 
 * [stored procedures](sql-data-warehouse-develop-stored-procedures.md)
 * [labels](sql-data-warehouse-develop-label.md)

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-data-types.md

@@ -1,6 +1,6 @@
 ---
 title: Defining data types
-description: Recommendations for defining table data types in Azure SQL Data Warehouse. 
+description: Recommendations for defining table data types in Synapse SQL pool. 
 services: synapse-analytics
 author: XiaoyuMSFT
 manager: craigg
@@ -13,24 +13,24 @@ ms.reviewer: igorstan
 ms.custom: seo-lt-2019
 ---
 
-# Table data types in Azure SQL Data Warehouse
-Recommendations for defining table data types in Azure SQL Data Warehouse. 
+# Table data types in Synapse SQL pool
+Included in this article are recommendations for defining table data types in SQL pool. 
 
-## What are the data types?
+## Supported data types
 
-SQL Data Warehouse supports the most commonly used data types. For a list of the supported data types, see [data types](/sql/t-sql/statements/create-table-azure-sql-data-warehouse#DataTypes) in the CREATE TABLE statement. 
+SQL pool supports the most commonly used data types. For a list of the supported data types, see [data types](/sql/t-sql/statements/create-table-azure-sql-data-warehouse#DataTypes) in the CREATE TABLE statement. 
 
 ## Minimize row length
 Minimizing the size of data types shortens the row length, which leads to better query performance. Use the smallest data type that works for your data. 
 
 - Avoid defining character columns with a large default length. For example, if the longest value is 25 characters, then define your column as VARCHAR(25). 
-- Avoid using [NVARCHAR][NVARCHAR] when you only need VARCHAR.
+- Avoid using [NVARCHAR](/sql/t-sql/data-types/nchar-and-nvarchar-transact-sql) when you only need VARCHAR.
 - When possible, use NVARCHAR(4000) or VARCHAR(8000) instead of NVARCHAR(MAX) or VARCHAR(MAX).
 
-If you are using PolyBase external tables to load your tables, the defined length of the table row cannot exceed 1 MB. When a row with variable-length data exceeds 1 MB, you can load the row with BCP, but not with PolyBase.
+If you're using PolyBase external tables to load your tables, the defined length of the table row can't exceed 1 MB. When a row with variable-length data exceeds 1 MB, you can load the row with BCP, but not with PolyBase.
 
 ## Identify unsupported data types
-If you are migrating your database from another SQL database, you might encounter data types that are not supported in SQL Data Warehouse. Use this query to discover unsupported data types in your existing SQL schema.
+If you're migrating your database from another SQL database, you might find data types that aren't supported in SQL pool. Use the following query to discover unsupported data types in your existing SQL schema:
 
 ```sql
 SELECT  t.[name], c.[name], c.[system_type_id], c.[user_type_id], y.[is_user_defined], y.[name]
@@ -44,7 +44,7 @@ WHERE y.[name] IN ('geography','geometry','hierarchyid','image','text','ntext','
 
 ## <a name="unsupported-data-types"></a>Workarounds for unsupported data types
 
-The following list shows the data types that SQL Data Warehouse does not support and gives alternatives that you can use instead of the unsupported data types.
+The following list shows the data types that SQL pool doesn't support and gives useful alternatives for unsupported data types.
 
 | Unsupported data type | Workaround |
 | --- | --- |
@@ -56,11 +56,12 @@ The following list shows the data types that SQL Data Warehouse does not support
 | [ntext](/sql/t-sql/data-types/ntext-text-and-image-transact-sql) |[nvarchar](/sql/t-sql/data-types/nchar-and-nvarchar-transact-sql) |
 | [sql_variant](/sql/t-sql/data-types/sql-variant-transact-sql) |Split column into several strongly typed columns. |
 | [table](/sql/t-sql/data-types/table-transact-sql) |Convert to temporary tables. |
-| [timestamp](/sql/t-sql/data-types/date-and-time-types) |Rework code to use [datetime2](/sql/t-sql/data-types/datetime2-transact-sql) and the [CURRENT_TIMESTAMP](/sql/t-sql/functions/current-timestamp-transact-sql) function. Only constants are supported as defaults, therefore current_timestamp cannot be defined as a default constraint. If you need to migrate row version values from a timestamp typed column, then use [BINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) or [VARBINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) for NOT NULL or NULL row version values. |
+| [timestamp](/sql/t-sql/data-types/date-and-time-types) |Rework code to use [datetime2](/sql/t-sql/data-types/datetime2-transact-sql) and the [CURRENT_TIMESTAMP](/sql/t-sql/functions/current-timestamp-transact-sql) function. Only constants are supported as defaults, so current_timestamp can't be defined as a default constraint. If you need to migrate row version values from a timestamp typed column, use [BINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) or [VARBINARY](/sql/t-sql/data-types/binary-and-varbinary-transact-sql)(8) for NOT NULL or NULL row version values. |
 | [xml](/sql/t-sql/xml/xml-transact-sql) |[varchar](/sql/t-sql/data-types/char-and-varchar-transact-sql) |
 | [user-defined type](/sql/relational-databases/native-client/features/using-user-defined-types) |Convert back to the native data type when possible. |
 | default values | Default values support literals and constants only. |
 
 
 ## Next steps
+
 For more information on developing tables, see [Table Overview](sql-data-warehouse-tables-overview.md).