resolving warnings

Author: julieMSFT

articles/sql-data-warehouse/sql-data-warehouse-troubleshoot.md

@@ -29,14 +29,14 @@ This article lists common troubleshooting question.
 | Issue                                                        | Resolution                                                   |
 | :----------------------------------------------------------- | :----------------------------------------------------------- |
 | Visual Studio object explorer is missing AAD users           | This is a known issue.  As a workaround, view the users in [sys.database_principals](https://docs.microsoft.com/sql/relational-databases/system-catalog-views/sys-database-principals-transact-sql?view=sql-server-ver15).  See [Authentication to Azure Synapse](sql-data-warehouse-authentication.md) to learn more about using Azure Active Directory with SQL Analytics. |
-| Manual scripting, using the scripting wizard, or connecting via SSMS is slow, not responding, or producing errors | Ensure that users have been created in the master database. In scripting options, also make sure that the engine edition is set as “Microsoft Azure SQL Data Warehouse Edition” and engine type is “Microsoft Azure SQL Database”. |
+| Manual scripting, using the scripting wizard, or connecting via SSMS is slow, not responding, or producing errors | Ensure that users have been created in the master database. In scripting options, also make sure that the engine edition is set as "Microsoft Azure SQL Data Warehouse Edition" and engine type is "Microsoft Azure SQL Database". |
 | Generate scripts fails in SSMS                               | Generating a script for SQL Analytics fails if the option "Generate script for dependent objects" option is set to "True." As a workaround, users must manually go to **Tools -> Options ->SQL Server Object Explorer -> Generate script for dependent options and set to false** |
 
 ## Performance
 | Issue                                                        | Resolution                                                   |
 | :----------------------------------------------------------- | :----------------------------------------------------------- |
 | Query performance troubleshooting                            | If you are trying to troubleshoot a particular query, start with [Learning how to monitor your queries](../sql-data-warehouse/sql-data-warehouse-manage-monitor.md#monitor-query-execution). |
-| TempDB space issues | [Monitor TempDB](../sql-data-warehouse/sql-data-warehouse-manage-monitor.md#monitor-tempdb) space usage.  Common causes for running out of TempDB space are:<br>- Not enough resources allocated to the query causing data to spill to TempDB.  See [Workload management](resource-classes-for-workload-management.md) <br>- Statistics are missing or out of date causing excessive data movement.  See [Maintaining table statistics](sql-data-warehouse-tables-statistics.md) for details on how to create statistics<br>- TempDB space is allocated per service level.  [Scaling your SQL pool](../sql-data-warehouse/sql-data-warehouse-manage-compute-overview.md#scaling-compute) to a higher DWU setting allocates more TempDB space.|
+| TempDB space issues | [Monitor TempDB](../sql-data-warehouse/sql-data-warehouse-manage-monitor.md#monitor-tempdb) space usage.  Common causes for running out of TempDB space are:<br>- Not enough resources allocated to the query causing data to spill to TempDB.  See [Workload management](resource-classes-for-workload-management.md) <br>- Statistics are missing or out of date causing excessive data movement.  See [Maintaining table statistics](sql-data-warehouse-tables-statistics.md) for details on how to create statistics<br>- TempDB space is allocated per service level.  [Scaling your SQL pool](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-manage-compute-overview.md#scaling-compute) to a higher DWU setting allocates more TempDB space.|
 | Poor query performance and plans often is a result of missing statistics | The most common cause of poor performance is lack of statistics on your tables.  See [Maintaining table statistics](sql-data-warehouse-tables-statistics.md) for details on how to create statistics and why they are critical to your performance. |
 | Low concurrency / queries queued                             | Understanding [Workload management](resource-classes-for-workload-management.md) is important in order to understand how to balance memory allocation with concurrency. |
 | How to implement best practices                              | The best place to start to learn ways to improve query performance is [SQL Analytics best practices](sql-data-warehouse-best-practices.md) article. |
@@ -57,8 +57,8 @@ This article lists common troubleshooting question.
 | :------------------------------------ | :----------------------------------------------------------- |
 | Unsupported SQL Database features     | See [Unsupported table features](../sql-data-warehouse/sql-data-warehouse-tables-overview.md#unsupported-table-features). |
 | Unsupported SQL Database data types   | See [Unsupported data types](../sql-data-warehouse/sql-data-warehouse-tables-data-types.md#identify-unsupported-data-types).        |
-| DELETE and UPDATE limitations         | See [UPDATE workarounds](../sql-data-warehouse/sql-data-warehouse-develop-ctas.md#ansi-join-replacement-for-update-statements), [DELETE workarounds](../sql-data-warehouse/sql-data-warehouse-develop-ctas.md#ansi-join-replacement-for-delete-statements) and [Using CTAS to work around unsupported UPDATE and DELETE syntax](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-ctas.md). |
-| MERGE statement is not supported      | See [MERGE workarounds](../sql-data-warehouse/sql-data-warehouse-develop-ctas.md#replace-merge-statements).                  |
+| DELETE and UPDATE limitations         | See [UPDATE workarounds](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-ctas.md#ansi-join-replacement-for-update-statements), [DELETE workarounds](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-ctas.md#ansi-join-replacement-for-delete-statements) and [Using CTAS to work around unsupported UPDATE and DELETE syntax](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-ctas.md). |
+| MERGE statement is not supported      | See [MERGE workarounds](../synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-ctas.md#replace-merge-statements).                  |
 | Stored procedure limitations          | See [Stored procedure limitations](../sql-data-warehouse/sql-data-warehouse-develop-stored-procedures.md#limitations) to understand some of the limitations of stored procedures. |
 | UDFs do not support SELECT statements | This is a current limitation of our UDFs.  See [CREATE FUNCTION](https://docs.microsoft.com/sql/t-sql/statements/create-function-sql-data-warehouse?view=aps-pdw-2016-au7) for the syntax we support. |
 

articles/synapse-analytics/sql-data-warehouse/media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-off.png

@@ -31,23 +31,23 @@ To enable TDE, follow the steps below:
 1. Open the database in the [Azure portal](https://portal.azure.com)
 2. In the database blade, click the **Settings** button
 3. Select the **Transparent data encryption** option
-   ![][1]
+   ![portal settings](./media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings.png)
 4. Select the **On** setting
-   ![][2]
+   ![portal settings on](./media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-on.png)
 5. Select **Save**
-   ![][3]  
+   ![portal settings save](./media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-save.png)  
 
 ## Disabling Encryption
 To disable TDE, follow the steps below:
 
 1. Open the database in the [Azure portal](https://portal.azure.com)
 2. In the database blade, click the **Settings** button
 3. Select the **Transparent data encryption** option
-   ![][1]
+   ![portal settings](./media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings.png)
 4. Select the **Off** setting
-   ![][4]
+   ![portal settings off](./media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-off.png)
 5. Select **Save**
-   ![][5]  
+   ![portal setting save 2](./media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-save2.png)  
 
 ## Encryption DMVs
 Encryption can be confirmed with the following DMVs:

articles/synapse-analytics/sql-data-warehouse/media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-on.png

@@ -2,7 +2,7 @@
 title: Install Visual Studio 2019 
 description: Install Visual Studio and SQL Server Development Tools (SSDT) for SQL Analytics
 services: sql-data-warehouse
-ms.custom: vs-azure
+ms.custom: vs-azure, azure-synapse
 ms.workload: azure-vs
 author: kevinvngo
 manager: craigg
@@ -12,7 +12,6 @@ ms.subservice: development
 ms.date: 02/04/2020
 ms.author: kevin
 ms.reviewer: igorstan
-ms.custom: azure-synapse
 ---
 
 # Getting started with Visual Studio 2019
@@ -45,15 +44,10 @@ There are times when feature releases for SQL Analytics may not include support
 
 ## Next steps
 
-Now that you have the latest version of SSDT, you're ready to [connect][connect] to your SQL pool.
+Now that you have the latest version of SSDT, you're ready to [connect](../../sql-data-warehouse/sql-data-warehouse-query-visual-studio.md) to your SQL pool.
 
-<!--Anchors-->
 
-<!--Image references-->
 
-<!--Articles-->
-
-[connect]: ./sql-data-warehouse-query-visual-studio.md
 
 <!--Other-->
 

articles/synapse-analytics/sql-data-warehouse/media/sql-data-warehouse-security-tde/sql-data-warehouse-security-tde-portal-settings-save.png

@@ -119,7 +119,7 @@ To check the SQL pool state, see the [PowerShell](quickstart-scale-compute-power
 
 ## Permissions
 
-Scaling the SQL pool requires the permissions described in [ALTER DATABASE](/sql/t-sql/statements/alter-database-azure-sql-data-warehouse).  Pause and Resume require the [SQL DB Contributor](../role-based-access-control/built-in-roles.md#sql-db-contributor) permission, specifically Microsoft.Sql/servers/databases/action.
+Scaling the SQL pool requires the permissions described in [ALTER DATABASE](/sql/t-sql/statements/alter-database-azure-sql-data-warehouse).  Pause and Resume require the [SQL DB Contributor](../../role-based-access-control/built-in-roles.md#sql-db-contributor) permission, specifically Microsoft.Sql/servers/databases/action.
 
 
 ## Next steps