synapse SQL next steps

Kat-Campise · Kat-Campise · commit 41f65d7d86c4 · 2020-04-08T13:11:53.000-07:00
diff --git a/articles/synapse-analytics/sql/access-control.md b/articles/synapse-analytics/sql/access-control.md
@@ -164,4 +164,8 @@ REVOKE CONTROL ON DATABASE::<SQLpoolname> TO <workspacename>;
 
 --Deleting the user in the DB
 DROP USER [<workspacename>];
-```
+```
+
+## Next steps
+
+For an overview of access and control in SQL Analytics, see [SQL Analytics access control](../sql/access-control.md). To learn more about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx). Additional information about database roles, can be found in the [Database roles](https://msdn.microsoft.com/library/ms189121.aspx) article.
diff --git a/articles/synapse-analytics/sql/active-directory-authentication.md b/articles/synapse-analytics/sql/active-directory-authentication.md
@@ -115,9 +115,7 @@ The following authentication methods are supported for Azure AD server principal
 
 ## Next steps
 
-- For an overview of access and control in SQL Analytics, see [SQL Analytics access control](../sql/access-control.md).
-- For more information about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx).
-- For more information about database roles, see [Database roles](https://msdn.microsoft.com/library/ms189121.aspx).
+For an overview of access and control in SQL Analytics, see [SQL Analytics access control](../sql/access-control.md). To learn more about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx). Additional information about database roles, can be found in the [Database roles](https://msdn.microsoft.com/library/ms189121.aspx) article.
 
 <!--Image references-->
 
diff --git a/articles/synapse-analytics/sql/best-practices-sql-on-demand.md b/articles/synapse-analytics/sql/best-practices-sql-on-demand.md
@@ -63,4 +63,4 @@ As CETAS generates Parquet files, statistics will be automatically created when
 
 ## Next steps
 
-Review the [Troubleshooting](../sql-data-warehouse/sql-data-warehouse-troubleshoot.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) article for common issues and solutions. If you're working with SQL pools rather than SQL on-demand, please see the [Best Practices for SQL pools](best-practices-sql-pool.md) article for specific guidance.
+Review the [Troubleshooting](../sql-data-warehouse/sql-data-warehouse-troubleshoot.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) article for common issues and solutions. If you're working with SQL pool rather than SQL on-demand, please see the [Best Practices for SQL pool](best-practices-sql-pool.md) article for specific guidance.
diff --git a/articles/synapse-analytics/sql/develop-transaction-best-practices.md b/articles/synapse-analytics/sql/develop-transaction-best-practices.md
@@ -400,7 +400,11 @@ END
 ```
 
 ## Pause and scaling guidance
-Azure Synapse Analytics lets you [pause, resume, and scale](../sql-data-warehouse/sql-data-warehouse-manage-compute-overview.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) your SQL pool on demand. When you pause or scale your SQL pool, it is important to understand that any in-flight transactions are terminated immediately; causing any open transactions to be rolled back. If your workload had issued a long running and incomplete data modification prior to the pause or scale operation, then this work will need to be undone. This undoing might impact the time it takes to pause or scale your SQL pool. 
+Azure Synapse Analytics lets you [pause, resume, and scale](../sql-data-warehouse/sql-data-warehouse-manage-compute-overview.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) your SQL pool on demand. 
+
+When you pause or scale your SQL pool, it is important to understand that any in-flight transactions are terminated immediately; causing any open transactions to be rolled back. 
+
+If your workload had issued a long running and incomplete data modification prior to the pause or scale operation, then this work will need to be undone. This undoing might impact the time it takes to pause or scale your SQL pool. 
 
 > [!IMPORTANT]
 > Both `UPDATE` and `DELETE` are fully logged operations and so these undo/redo operations can take significantly longer than equivalent minimally logged operations. 
diff --git a/articles/synapse-analytics/sql/develop-transactions.md b/articles/synapse-analytics/sql/develop-transactions.md
@@ -22,10 +22,14 @@ As you would expect, SQL pool supports transactions as part of the data warehous
 
 ## Transaction isolation levels
 
-SQL pool implements ACID transactions. The isolation level of the transactional support is default to READ UNCOMMITTED.  You can change it to READ COMMITTED SNAPSHOT ISOLATION by turning ON the READ_COMMITTED_SNAPSHOT database option for a user database when connected to the master database.  Once enabled, all transactions in this database are executed under READ COMMITTED SNAPSHOT ISOLATION and setting READ UNCOMMITTED on session level will not be honored. Check [ALTER DATABASE SET options (Transact-SQL)](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-set-options?view=azure-sqldw-latest) for details.
+SQL pool implements ACID transactions. The isolation level of the transactional support is default to READ UNCOMMITTED.  You can change it to READ COMMITTED SNAPSHOT ISOLATION by turning ON the READ_COMMITTED_SNAPSHOT database option for a user database when connected to the master database.  
+
+Once enabled, all transactions in this database are executed under READ COMMITTED SNAPSHOT ISOLATION and setting READ UNCOMMITTED on session level will not be honored. Check [ALTER DATABASE SET options (Transact-SQL)](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-set-options?view=azure-sqldw-latest) for details.
 
 ## Transaction size
-A single data modification transaction is limited in size. The limit is applied per distribution. Therefore, the total allocation can be calculated by multiplying the limit by the distribution count. To approximate the maximum number of rows in the transaction divide the distribution cap by the total size of each row. For variable length columns, consider taking an average column length rather than using the maximum size.
+A single data modification transaction is limited in size. The limit is applied per distribution. Therefore, the total allocation can be calculated by multiplying the limit by the distribution count. 
+
+To approximate the maximum number of rows in the transaction divide the distribution cap by the total size of each row. For variable length columns, consider taking an average column length rather than using the maximum size.
 
 In the table below the following assumptions have been made:
 
@@ -199,5 +203,5 @@ They are as follows:
 * No support for DDL such as CREATE TABLE inside a user-defined transaction
 
 ## Next steps
-To learn more about optimizing transactions, see [Transactions best practices](../sql-data-warehouse/sql-data-warehouse-develop-best-practices-transactions.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json). Additional best practices guides are also provided for [SQL pools](best-practices-sql-pool.md) and [SQL on-demand (preview)](on-demand.md).
+To learn more about optimizing transactions, see [Transactions best practices](../sql-data-warehouse/sql-data-warehouse-develop-best-practices-transactions.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json). Additional best practices guides are also provided for [SQL pool](best-practices-sql-pool.md) and [SQL on-demand (preview)](on-demand.md).
 
diff --git a/articles/synapse-analytics/sql/get-started-power-bi-professional.md b/articles/synapse-analytics/sql/get-started-power-bi-professional.md
@@ -103,6 +103,5 @@ Write URL for the database and name of the database where view is residing.
 
 ## Next steps
 
-Advance to the next article to learn how to connect to SQL on-demand using Azure Data Studio.
-> [!div class="nextstepaction"]
-> [Query storage files](get-started-azure-data-studio.md)
+Advance to [Query storage files](get-started-azure-data-studio.md) to learn how to connect to SQL on-demand using Azure Data Studio.
+ 
diff --git a/articles/synapse-analytics/sql/mfa-authentication.md b/articles/synapse-analytics/sql/mfa-authentication.md
@@ -12,7 +12,9 @@ ms.reviewer: jrasnick
 
 # Using Multi-factor AAD authentication with SQL Analytics (SSMS support for MFA)
 
-SQL Analytics support connections from SQL Server Management Studio (SSMS) using *Active Directory Universal Authentication*. This article discusses the differences between the various authentication options, and also the limitations associated with using Universal Authentication. 
+SQL Analytics support connections from SQL Server Management Studio (SSMS) using *Active Directory Universal Authentication*. 
+
+This article discusses the differences between the various authentication options, and also the limitations associated with using Universal Authentication. 
 
 **Download the latest SSMS** - On the client computer, download the latest version of SSMS, from [Download SQL Server Management Studio (SSMS)](https://msdn.microsoft.com/library/mt238290.aspx). 
 
@@ -42,15 +44,35 @@ For a description of Multi-Factor Authentication, see [Multi-Factor Authenticati
 ### Azure AD domain name or tenant ID parameter   
 
 
-Beginning with [SSMS version 17](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms), users that are imported into the current Active Directory from other Azure Active Directories as guest users, can provide the Azure AD domain name, or tenant ID when they connect. Guest users include users invited from other Azure ADs, Microsoft accounts such as outlook.com, hotmail.com, live.com, or other accounts like gmail.com. This information, allows **Active Directory Universal with MFA Authentication** to identify the correct authenticating authority. This option is also required to support Microsoft accounts (MSA) such as outlook.com, hotmail.com, live.com, or non-MSA accounts. All these users who want to be authenticated using Universal Authentication must enter their Azure AD domain name or tenant ID. This parameter represents the current Azure AD domain name/tenant ID the Azure Server is linked with. For example, if Azure Server is associated with Azure AD domain `contosotest.onmicrosoft.com` where user `joe@contosodev.onmicrosoft.com` is hosted as an imported user from Azure AD domain `contosodev.onmicrosoft.com`, the domain name required to authenticate this user is `contosotest.onmicrosoft.com`. When the user is a native user of the Azure AD linked to Azure Server, and is not an MSA account, no domain name or tenant ID is required. To enter the parameter (beginning with SSMS version 17.2), in the **Connect to Database** dialog box, complete the dialog box, selecting **Active Directory - Universal with MFA** authentication, click **Options**, complete the **User name** box, and then click the **Connection Properties** tab. Check the **AD domain name or tenant ID** box, and provide authenticating authority, such as the domain name (**contosotest.onmicrosoft.com**) or the GUID of the tenant ID.  
+Beginning with [SSMS version 17](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms), users that are imported into the current Active Directory from other Azure Active Directories as guest users, can provide the Azure AD domain name, or tenant ID when they connect. 
+
+Guest users include users invited from other Azure ADs, Microsoft accounts such as outlook.com, hotmail.com, live.com, or other accounts like gmail.com. This information, allows **Active Directory Universal with MFA Authentication** to identify the correct authenticating authority. This option is also required to support Microsoft accounts (MSA) such as outlook.com, hotmail.com, live.com, or non-MSA accounts. 
+
+All these users who want to be authenticated using Universal Authentication must enter their Azure AD domain name or tenant ID. This parameter represents the current Azure AD domain name/tenant ID the Azure Server is linked with. 
+
+For example, if Azure Server is associated with Azure AD domain `contosotest.onmicrosoft.com` where user `joe@contosodev.onmicrosoft.com` is hosted as an imported user from Azure AD domain `contosodev.onmicrosoft.com`, the domain name required to authenticate this user is `contosotest.onmicrosoft.com`. 
+
+When the user is a native user of the Azure AD linked to Azure Server, and is not an MSA account, no domain name or tenant ID is required. 
+
+To enter the parameter (beginning with SSMS version 17.2), in the **Connect to Database** dialog box, complete the dialog box, selecting **Active Directory - Universal with MFA** authentication, click **Options**, complete the **User name** box, and then click the **Connection Properties** tab. 
+
+Check the **AD domain name or tenant ID** box, and provide authenticating authority, such as the domain name (**contosotest.onmicrosoft.com**) or the GUID of the tenant ID.  
    ![mfa-tenant-ssms](./media/mfa-authentication/mfa-tenant-ssms.png)
 
 If you are running SSMS 18.x or later then the AD domain name or tenant ID is no longer needed for guest users because 18.x or later automatically recognizes it.
 
    ![mfa-tenant-ssms](./media/mfa-authentication/mfa-no-tenant-ssms.png)
 
 ### Azure AD business to business support   
-Azure AD users supported for Azure AD B2B scenarios as guest users (see [What is Azure B2B collaboration](../../active-directory/b2b/what-is-b2b.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) can connect to SQL Analytics only as part of members of a group created in current Azure AD and mapped manually using the Transact-SQL `CREATE USER` statement in a given database. For example, if `steve@gmail.com` is invited to Azure AD `contosotest` (with the Azure Ad domain `contosotest.onmicrosoft.com`), an Azure AD group, such as `usergroup` must be created in the Azure AD that contains the `steve@gmail.com` member. Then, this group must be created for a specific  database (that is, MyDatabase) by Azure AD SQL admin or Azure AD DBO  by executing a Transact-SQL `CREATE USER [usergroup] FROM EXTERNAL PROVIDER` statement. After the database user is created, then the user `steve@gmail.com` can log in to `MyDatabase` using the SSMS authentication option `Active Directory – Universal with MFA support`. The usergroup, by default, has only the connect permission and any further data access that will need to be granted in the normal way. Note that user `steve@gmail.com` as a guest user must check the box and add the AD domain name `contosotest.onmicrosoft.com` in the SSMS **Connection Property** dialog box. The **AD domain name or tenant ID** option is only supported for the Universal with MFA connection options, otherwise it is greyed out.
+Azure AD users supported for Azure AD B2B scenarios as guest users (see [What is Azure B2B collaboration](../../active-directory/b2b/what-is-b2b.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) can connect to SQL Analytics only as part of members of a group created in current Azure AD and mapped manually using the Transact-SQL `CREATE USER` statement in a given database. 
+
+For example, if `steve@gmail.com` is invited to Azure AD `contosotest` (with the Azure Ad domain `contosotest.onmicrosoft.com`), an Azure AD group, such as `usergroup` must be created in the Azure AD that contains the `steve@gmail.com` member. Then, this group must be created for a specific  database (that is, MyDatabase) by Azure AD SQL admin or Azure AD DBO  by executing a Transact-SQL `CREATE USER [usergroup] FROM EXTERNAL PROVIDER` statement. 
+
+After the database user is created, then the user `steve@gmail.com` can log in to `MyDatabase` using the SSMS authentication option `Active Directory – Universal with MFA support`. 
+
+The usergroup, by default, has only the connect permission and any further data access that will need to be granted in the normal way. 
+
+Note that user `steve@gmail.com` as a guest user must check the box and add the AD domain name `contosotest.onmicrosoft.com` in the SSMS **Connection Property** dialog box. The **AD domain name or tenant ID** option is only supported for the Universal with MFA connection options, otherwise it is greyed out.
 
 ## Universal Authentication limitations for SQL Analytics
 - SSMS and SqlPackage.exe are the only tools currently enabled for MFA through Active Directory Universal Authentication.
@@ -59,4 +81,7 @@ Azure AD users supported for Azure AD B2B scenarios as guest users (see [What is
 - SSMS version 17.2 provides DacFx Wizard support for Export/Extract/Deploy Data database. Once a specific user is authenticated through the initial authentication dialog using Universal Authentication, the DacFx Wizard functions the same way it does for all other authentication methods.
 - The SSMS Table Designer does not support Universal Authentication.
 - There are no additional software requirements for Active Directory Universal Authentication except that you must use a supported version of SSMS.  
-- The Active Directory Authentication Library (ADAL) version for Universal authentication was updated to its latest ADAL.dll 3.13.9 available released version. See [Active Directory Authentication Library 3.14.1](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory/).  
+- The Active Directory Authentication Library (ADAL) version for Universal authentication was updated to its latest ADAL.dll 3.13.9 available released version. See [Active Directory Authentication Library 3.14.1](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory/).  
+
+## Next steps
+For more information, see the [Connect to SQL Analytics with SQL Server Management Studio](get-started-ssms.md) article. 
diff --git a/articles/synapse-analytics/sql/on-demand-workspace-overview.md b/articles/synapse-analytics/sql/on-demand-workspace-overview.md
@@ -145,6 +145,6 @@ A user that is logged into SQL on-demand service must be authorized to access an
 
 
 ## Next steps
-
+Additional information on endpoint connection and querying files can be found in the following articles: 
 - [Connect to your endpoint](connect-overview.md)
 - [Query your files](develop-storage-files-overview.md)
diff --git a/articles/synapse-analytics/sql/on-demand.md b/articles/synapse-analytics/sql/on-demand.md
@@ -55,6 +55,6 @@ Different professional roles can benefit from SQL on-demand:
 - BI Professionals can quickly create Power BI reports on top of data in the lake and Spark tables. 
 
 ## Next steps
-
+For more information, see the following articles:
 - [Connect to your endpoint](connect-overview.md)
 - [Query your files](develop-storage-files-overview.md)
diff --git a/articles/synapse-analytics/sql/overview-features.md b/articles/synapse-analytics/sql/overview-features.md
@@ -123,3 +123,9 @@ Data that is analyzed can be stored in various storage formats. The following ta
 | JSON | Yes | [Yes](query-json-files.md) |
 | [Delta-lake](https://delta.io/) | No | No |
 | [CDM](https://docs.microsoft.com/common-data-model/) | No | No |
+
+## Next steps
+Additional information on best practices for SQL pool and SQL on-demand can be found in the following articles:
+
+- [Best Practices for SQL pool](best-practices-sql-pool.md)
+- [Best practices for SQL on-demand](best-practices-sql-on-demand)
diff --git a/articles/synapse-analytics/sql/query-json-files.md b/articles/synapse-analytics/sql/query-json-files.md
@@ -137,7 +137,7 @@ WHERE
 
 ## Next steps
 
-The next article in this series will demonstrate how to:
+The next articles in this series will demonstrate how to:
 
 - [Querying folders and multiple files](query-folders-multiple-csv-files.md)
 - [Create and use views](create-use-views.md).
diff --git a/articles/synapse-analytics/sql/query-single-csv-file.md b/articles/synapse-analytics/sql/query-single-csv-file.md
@@ -230,6 +230,6 @@ WITH (
 ## Next steps
 
 The next articles will show you how to:
-> [!div class="nextstepaction"]
-> [Querying Parquet files](query-parquet-files.md)
-> [Querying folders and multiple files](query-folders-multiple-csv-files.md)
+
+- [Querying Parquet files](query-parquet-files.md)
+- [Querying folders and multiple files](query-folders-multiple-csv-files.md)
diff --git a/articles/synapse-analytics/sql/reference-collation-types.md b/articles/synapse-analytics/sql/reference-collation-types.md
diff --git a/articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md b/articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md
diff --git a/articles/synapse-analytics/sql/sql-authentication.md b/articles/synapse-analytics/sql/sql-authentication.md
diff --git a/articles/synapse-analytics/sql/tutorial-connect-power-bi-desktop.md b/articles/synapse-analytics/sql/tutorial-connect-power-bi-desktop.md
diff --git a/articles/synapse-analytics/sql/tutorial-data-analyst.md b/articles/synapse-analytics/sql/tutorial-data-analyst.md

Original file line number	Diff line number	Diff line change
`@@ -63,4 +63,4 @@ As CETAS generates Parquet files, statistics will be automatically created when`
`63`	`63`
`64`	`64`	`## Next steps`
`65`	`65`
`66`		`-Review the [Troubleshooting](../sql-data-warehouse/sql-data-warehouse-troubleshoot.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) article for common issues and solutions. If you're working with SQL pools rather than SQL on-demand, please see the [Best Practices for SQL pools](best-practices-sql-pool.md) article for specific guidance.`
	`66`	`+Review the [Troubleshooting](../sql-data-warehouse/sql-data-warehouse-troubleshoot.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) article for common issues and solutions. If you're working with SQL pool rather than SQL on-demand, please see the [Best Practices for SQL pool](best-practices-sql-pool.md) article for specific guidance.`