Merge pull request #115312 from Kat-Campise/sql_articles_2

sql articles 2

Author: ttorble

articles/synapse-analytics/sql/create-use-views.md

@@ -21,7 +21,7 @@ Your first step is to create a database where the view will be created and initi
 
 ## Create a view
 
-You can create views the same way you create regular SQL Server views. The query below creates view that reads *population.csv* file.
+You can create views the same way you create regular SQL Server views. The following query creates view that reads *population.csv* file.
 
 > [!NOTE]
 > Change the first line in the query, i.e., [mydbname], so you're using the database you created.

articles/synapse-analytics/sql/develop-openrowset.md

@@ -52,8 +52,8 @@ The storage administrator must also enable a user to access the files by providi
 `OPENROWSET` use the following rules to determine how to authenticate to storage:
 - In `OPENROWSET` without `DATA_SOURCE` authentication mechanism depends on caller type.
   - AAD logins can access files only using their own [Azure AD identity](develop-storage-files-storage-access-control.md?tabs=user-identity#supported-storage-authorization-types) if Azure storage allows the Azure AD user to access underlying files (for example, if the caller has Storage Reader permission on storage) and if you [enable Azure AD passthrough authentication](develop-storage-files-storage-access-control.md#force-azure-ad-pass-through) on Synapse SQL service.
-  - SQL logins can also use `OPENROWSET` without `DATA_SOURCE` to access publicly available files, files protected using SAS token or Managed Identity of Synapse workspace. You would need to [create server-scoped credential](develop-storage-files-storage-access-control.md#examples) to allow access to storage files. 
-- In `OPENROWSET` with `DATA_SOURCE` authentication mechanism is defined in database scoped credential assigned to the referenced data source. This option enables you to access publicly available storage, or access storage using SAS token, Managed Identity of workspace, or [Azure AD identity of caller](develop-storage-files-storage-access-control.md?tabs=user-identity#supported-storage-authorization-types) (if caller is Azure AD principal). If `DATA_SOURCE` references Azure storage that is not public, you would need to [create database-scoped credential](develop-storage-files-storage-access-control.md#examples) and reference it in `DATA SOURCE` to allow access to storage files.
+  - SQL logins can also use `OPENROWSET` without `DATA_SOURCE` to access publicly available files, files protected using SAS token, or Managed Identity of Synapse workspace. You would need to [create server-scoped credential](develop-storage-files-storage-access-control.md#examples) to allow access to storage files. 
+- In `OPENROWSET` with `DATA_SOURCE` authentication mechanism is defined in database scoped credential assigned to the referenced data source. This option enables you to access publicly available storage, or access storage using SAS token, Managed Identity of workspace, or [Azure AD identity of caller](develop-storage-files-storage-access-control.md?tabs=user-identity#supported-storage-authorization-types) (if caller is Azure AD principal). If `DATA_SOURCE` references Azure storage that isn't public, you would need to [create database-scoped credential](develop-storage-files-storage-access-control.md#examples) and reference it in `DATA SOURCE` to allow access to storage files.
 
 Caller must have `REFERENCES` permission on credential to use it to authenticate to storage.
 
@@ -162,7 +162,7 @@ Specifies the field terminator to be used. The default field terminator is a com
 
 ROWTERMINATOR ='row_terminator'`
 
-Specifies the row terminator to be used. If row terminator is not specified one of default terminators will be used. Default terminators for PARSER_VERSION = '1.0' are \r\n, \n and \r. Default terminators for PARSER_VERSION = '2.0' are \r\n and \n.
+Specifies the row terminator to be used. If row terminator is not specified, one of default terminators will be used. Default terminators for PARSER_VERSION = '1.0' are \r\n, \n and \r. Default terminators for PARSER_VERSION = '2.0' are \r\n and \n.
 
 ESCAPE_CHAR = 'char'
 
@@ -186,18 +186,18 @@ Specifies compression method. Following compression method is supported:
 
 PARSER_VERSION = 'parser_version'
 
-Specifies parser version to be used when reading files. Currently supported CSV parser versions are 1.0 and 2.0
+Specifies parser version to be used when reading files. Currently supported CSV parser versions are 1.0 and 2.0:
 
 - PARSER_VERSION = '1.0'
 - PARSER_VERSION = '2.0'
 
-CSV parser version 1.0 is default and feature-rich, while 2.0 is built for performance and does not support all options and encodings. 
+CSV parser version 1.0 is default and feature rich, while 2.0 is built for performance and does not support all options and encodings. 
 
 CSV parser version 2.0 specifics:
 
 - Not all data types are supported.
-- Maximum row size limit is 8MB.
-- Following options are not supported: DATA_COMPRESSION.
+- Maximum row size limit is 8 MB.
+- Following options aren't supported: DATA_COMPRESSION.
 - Quoted empty string ("") is interpreted as empty string.
 
 ## Examples
@@ -229,9 +229,9 @@ FROM
     ) AS [r]
 ```
 
-If you are getting an error saying that the files cannot be listed, you need to enable access to public storage in Synapse SQL on-demand:
-- If you are using a SQL login you need to [create server-scoped credential that allows access to public storage](develop-storage-files-storage-access-control.md#examples).
-- If you are using an Azure AD principal to access public storage, you would need to [create server-scoped credential that allows access to public storage](develop-storage-files-storage-access-control.md#examples) and disable [Azure AD passthrough authentication](develop-storage-files-storage-access-control.md#disable-forcing-azure-ad-pass-through).
+If you're getting an error saying that the files cannot be listed, you need to enable access to public storage in Synapse SQL on-demand:
+- If you're using a SQL login, you need to [create server-scoped credential that allows access to public storage](develop-storage-files-storage-access-control.md#examples).
+- If you're using an Azure AD principal to access public storage, you would need to [create server-scoped credential that allows access to public storage](develop-storage-files-storage-access-control.md#examples) and disable [Azure AD passthrough authentication](develop-storage-files-storage-access-control.md#disable-forcing-azure-ad-pass-through).
 
 ## Next steps