Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr

Author: markingmyname

docs/database-engine/log-shipping/log-shipping-and-replication-sql-server.md

@@ -3,7 +3,7 @@ title: "Log Shipping and Replication (SQL Server)"
 description: Learn how log shipping applies the transaction log from every insertion, update, or deletion made on the primary database to the secondary database.
 author: MikeRayMSFT
 ms.author: mikeray
-ms.date: "03/14/2017"
+ms.date: "04/11/2023"
 ms.service: sql
 ms.subservice: log-shipping
 ms.topic: conceptual
@@ -24,7 +24,7 @@ helpviewer_keywords:
  For information about recovering databases involved in replication without any need to reconfigure replication, see [Back Up and Restore Replicated Databases](../../relational-databases/replication/administration/back-up-and-restore-replicated-databases.md).  
 
 > [!NOTE]  
->  We recommend using database mirroring, rather than log shipping, to provide availability for the publication database. For more information, see [Database Mirroring and Replication (SQL Server)](../../database-engine/database-mirroring/database-mirroring-and-replication-sql-server.md).  
+>  Use Always On availability groups, rather than log shipping, to provide availability for the publication database. For more information, see [Configure replication with Always On availability groups](../availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server.md).
   
 ## Requirements and Procedures for Replicating from the Secondary If the Primary Is Lost  
  Be aware of the following requirements and considerations:  
@@ -107,7 +107,5 @@ helpviewer_keywords:
 
 ## See Also  
  [SQL Server Replication](../../relational-databases/replication/sql-server-replication.md)   
- [About Log Shipping (SQL Server)](../../database-engine/log-shipping/about-log-shipping-sql-server.md)   
- [Database Mirroring and Replication (SQL Server)](../../database-engine/database-mirroring/database-mirroring-and-replication-sql-server.md)  
-  
-  
+ [About Log Shipping (SQL Server)](../../database-engine/log-shipping/about-log-shipping-sql-server.md)
+ [Configure replication with Always On availability groups](../availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server.md)

docs/relational-databases/native-client-ole-db-transactions/supporting-distributed-transactions.md

@@ -133,6 +133,7 @@ if (FAILED(pITransactionJoin->JoinTransaction(
 ```  
 
 ## See Also  
- [Transactions](../../relational-databases/native-client-ole-db-transactions/transactions.md)  
+ [Transactions](../../relational-databases/native-client-ole-db-transactions/transactions.md)
+ [MS DTC for Azure SQL Managed Instance](https://learn.microsoft.com/azure/azure-sql/managed-instance/distributed-transaction-coordinator-dtc)
 
 

docs/relational-databases/polybase/polybase-configure-s3-compatible.md

@@ -70,7 +70,7 @@ The following sample script creates a database scoped credential `s3-dc` in the
 ```sql
 USE [database_name];
 GO
-IF NOT EXISTS(SELECT * FROM sys.credentials WHERE name = 's3_dc')
+IF NOT EXISTS(SELECT * FROM sys.database_scoped_credentials WHERE name = 's3_dc')
 BEGIN
  CREATE DATABASE SCOPED CREDENTIAL s3_dc
  WITH IDENTITY = 'S3 Access Key',

docs/relational-databases/security/authentication-access/getting-started-with-database-engine-permissions.md

@@ -192,11 +192,11 @@ For a graphic showing the relationships among the [!INCLUDE[ssDE](../../../inclu
 
 - The permissions granted to users and user-defined fixed database roles can be examined by using the `sys.database_permissions` view.
 
-- Database role membership can be examined by using the `sys. sys.database_role_members` view.
+- Database role membership can be examined by using the `sys.database_role_members` view.
 
 - Server role membership can be examined by using the `sys.server_role_members` view. This view isn't available in [!INCLUDE[ssSDS](../../../includes/sssds-md.md)].
 
-- For additional security related views, see [Security Catalog Views (Transact-SQL)](../../../relational-databases/system-catalog-views/security-catalog-views-transact-sql.md) .
+- For additional security related views, see [Security Catalog Views (Transact-SQL)](../../../relational-databases/system-catalog-views/security-catalog-views-transact-sql.md).
 
 ## Examples
 

docs/relational-databases/system-catalog-views/sys-server-principals-transact-sql.md

@@ -27,9 +27,9 @@ monikerRange: ">=aps-pdw-2016||>=sql-server-2016||>=sql-server-linux-2017||=azur
 |-----------------|---------------|-----------------|  
 |**name**|**sysname**|Name of the principal. Is unique within a server.|  
 |**principal_id**|**int**|ID number of the Principal. Is unique within a server.|  
-|**sid**|**varbinary(85)**|SID (Security-IDentifier) of the principal. If Windows principal, then it matches Windows SID.|  
-|**type**|**char(1)**|Principal type:<br /><br /> S = SQL login<br /><br /> U = Windows login<br /><br /> G = Windows group<br /><br /> R = Server role<br /><br /> C = Login mapped to a certificate<br /><br /> E = External Login from Azure Active Directory<br /><br /> X = External group from Azure Active Directory group or applications<br /><br /> K = Login mapped to an asymmetric key|  
-|**type_desc**|**nvarchar(60)**|Description of the principal type:<br /><br /> SQL_LOGIN<br /><br /> WINDOWS_LOGIN<br /><br /> WINDOWS_GROUP<br /><br /> SERVER_ROLE<br /><br /> CERTIFICATE_MAPPED_LOGIN<br /><br /> EXTERNAL_LOGIN<br /><br /> EXTERNAL_GROUP<br /><br /> ASYMMETRIC_KEY_MAPPED_LOGIN|  
+|**sid**|**varbinary(85)**|SID (Security-IDentifier) of the principal.|  
+|**type**|**char(1)**|Principal type:<br /><br /> S = SQL login<br /> R = Server role<br /><br /> E = External Login from Azure Active Directory<br /><br /> X = External group from Azure Active Directory group or applications<br />|  
+|**type_desc**|**nvarchar(60)**|Description of the principal type:<br /><br /> SQL_LOGIN<br /><br /> SERVER_ROLE<br /><br /> EXTERNAL_LOGIN<br /><br /> EXTERNAL_GROUP<br />|  
 |**is_disabled**|**int**|1 = Login is disabled.|  
 |**create_date**|**datetime**|Time at which the principal was created.|  
 |**modify_date**|**datetime**|Time at which the principal definition was last modified.|  
@@ -40,26 +40,14 @@ monikerRange: ">=aps-pdw-2016||>=sql-server-2016||>=sql-server-linux-2017||=azur
 |**is_fixed_role**|**bit**|Returns 1 if the principal is one of the built-in server roles with fixed permissions. For more information, see [Server-Level Roles](../../relational-databases/security/authentication-access/server-level-roles.md).|  
 
 ## Permissions  
- Any login can see their own login name, the system logins, and the fixed server roles. To see other logins, requires ALTER ANY LOGIN, or a permission on the login. To see user-defined server roles, requires ALTER ANY SERVER ROLE, or membership in the role. 
- 
-Azure SQL Database: only members of the server role **##MS_LoginManager##** or the special database role loginmanager in `master` or the Azure AD admin and server sdmin can see all logins.
- 
+Any login can see their own login name, the system logins, and the fixed server roles. Only members of the server role **##MS_LoginManager##** or the special database role loginmanager in `master` or the Azure AD admin and server Admin can see all logins.
+
 
  [!INCLUDE[ssCatViewPerm](../../includes/sscatviewperm-md.md)] For more information, see [Metadata Visibility Configuration](../../relational-databases/security/metadata-visibility-configuration.md).  
+    
+> [!NOTE]  
+>  The permissions of fixed server roles do not appear in sys.server_permissions.
   
-## Examples  
- The following query lists the permissions explicitly granted or denied to server principals.  
-  
-> [!IMPORTANT]  
->  The permissions of fixed server roles (other than public) do not appear in sys.server_permissions. Therefore, server principals may have additional permissions not listed here.  
-  
-```  
-SELECT pr.principal_id, pr.name, pr.type_desc,   
-    pe.state_desc, pe.permission_name   
-FROM sys.server_principals AS pr   
-JOIN sys.server_permissions AS pe   
-    ON pe.grantee_principal_id = pr.principal_id;  
-```  
 
 ## See Also  
  [Security Catalog Views &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/security-catalog-views-transact-sql.md)   

docs/relational-databases/track-changes/track-data-changes-sql-server.md

@@ -24,8 +24,6 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 
 [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] provides two features that track changes to data in a database: [change data capture](#Capture) and [change tracking](#Tracking). These features enable applications to determine the DML changes (insert, update, and delete operations) that were made to user tables in a database. Change data capture and change tracking can be enabled on the same database; no special considerations are required. For the editions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that support change data capture and change tracking, see [Editions and supported features of SQL Server](../../sql-server/editions-and-components-of-sql-server-2019.md).
 
-Change tracking is supported by [!INCLUDE[ssazure_md](../../includes/ssazure_md.md)]. Change data capture is only supported in [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and Azure SQL Managed Instance.
-
 ## Benefits of using change data capture or change tracking
 
  The ability to query for data that has changed in a database is an important requirement for some applications to be efficient. Typically, to determine data changes, application developers must implement a custom tracking method in their applications by using a combination of triggers, **timestamp** columns, and additional tables. Creating these applications usually involves a lot of work to implement, leads to schema updates, and often carries a high performance overhead.

docs/t-sql/functions/openrowset-transact-sql.md

@@ -155,26 +155,27 @@ SELECT * FROM OPENROWSET(
    SINGLE_CLOB) AS DATA;
 ```
 
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
-Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1, the data_file can be in Azure Blob Storage. For examples, see [Examples of Bulk Access to Data in Azure Blob Storage](../../relational-databases/import-export/examples-of-bulk-access-to-data-in-azure-blob-storage.md).
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], the data_file can be in Azure Blob Storage. For examples, see [Examples of Bulk Access to Data in Azure Blob Storage](../../relational-databases/import-export/examples-of-bulk-access-to-data-in-azure-blob-storage.md).
 
 > [!IMPORTANT]
 > Azure SQL Database only supports reading from Azure Blob Storage.
 
 #### BULK Error handling options
 
 ##### ERRORFILE
+
 `ERRORFILE` ='*file_name*' specifies the file used to collect rows that have formatting errors and cannot be converted to an OLE DB rowset. These rows are copied into this error file from the data file "as is."
 
 The error file is created at the start of the command execution. An error will be raised if the file already exists. Additionally, a control file that has the extension .ERROR.txt is created. This file references each row in the error file and provides error diagnostics. After the errors have been corrected, the data can be loaded.
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
+
 Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], the `error_file_path` can be in Azure Blob Storage.
 
 ##### ERRORFILE_DATA_SOURCE_NAME
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
-Is a named external data source pointing to the Azure Blob storage location of the error file that will contain errors found during the import. The external data source must be created using the `TYPE = BLOB_STORAGE` option added in [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1. For more information, see [CREATE EXTERNAL DATA SOURCE](../../t-sql/statements/create-external-data-source-transact-sql.md).
+
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], is a named external data source pointing to the Azure Blob storage location of the error file that will contain errors found during the import. The external data source must be created using the `TYPE = BLOB_STORAGE`. For more information, see [CREATE EXTERNAL DATA SOURCE](../../t-sql/statements/create-external-data-source-transact-sql.md).
 
 ##### MAXERRORS
+
 `MAXERRORS` =*maximum_errors* specifies the maximum number of syntax errors or nonconforming rows, as defined in the format file, that can occur before OPENROWSET throws an exception. Until MAXERRORS is reached, OPENROWSET ignores each bad row, not loading it, and counts the bad row as one error.
 
 The default for *maximum_errors* is 10.
@@ -185,22 +186,29 @@ The default for *maximum_errors* is 10.
 #### BULK Data processing options
 
 ##### FIRSTROW
+
 `FIRSTROW` =*first_row*
+
 Specifies the number of the first row to load. The default is 1. This indicates the first row in the specified data file. The row numbers are determined by counting the row terminators. FIRSTROW is 1-based.
 
 ##### LASTROW
+
 `LASTROW` =*last_row*
+
 Specifies the number of the last row to load. The default is 0. This indicates the last row in the specified data file.
 
 ##### ROWS_PER_BATCH
+
 `ROWS_PER_BATCH` =*rows_per_batch*
+
 Specifies the approximate number of rows of data in the data file. This value should be of the same order as the actual number of rows.
 
 `OPENROWSET` always imports a data file as a single batch. However, if you specify *rows_per_batch* with a value > 0, the query processor uses the value of *rows_per_batch* as a hint for allocating resources in the query plan.
 
 By default, ROWS_PER_BATCH is unknown. Specifying ROWS_PER_BATCH = 0 is the same as omitting ROWS_PER_BATCH.
 
 ##### ORDER
+
 `ORDER` ( { *column* [ ASC | DESC ] } [ ,... *n* ] [ UNIQUE ] )
 An optional hint that specifies how the data in the data file is sorted. By default, the bulk operation assumes the data file is unordered. Performance might improve if the order specified can be exploited by the query optimizer to generate a more efficient query plan. Examples for when specifying a sort can be beneficial include the following:
 
@@ -210,22 +218,26 @@ An optional hint that specifies how the data in the data file is sorted. By defa
 - Using the rowset as a source table in the FROM clause of a query, where the sort and join columns match.
 
 ##### UNIQUE
+
 `UNIQUE` specifies that the data file does not have duplicate entries.
 
 If the actual rows in the data file are not sorted according to the order that is specified, or if the UNIQUE hint is specified and duplicates keys are present, an error is returned.
 
 Column aliases are required when ORDER is used. The column alias list must reference the derived table that is being accessed by the BULK clause. The column names that are specified in the ORDER clause refer to this column alias list. Large value types (**varchar(max)**, **nvarchar(max)**, **varbinary(max)**, and **xml**) and large object (LOB) types (**text**, **ntext**, and **image**) columns cannot be specified.
 
 ##### SINGLE_BLOB
+
 Returns the contents of *data_file* as a single-row, single-column rowset of type **varbinary(max)**.
 
 > [!IMPORTANT]
 > We recommend that you import XML data only using the SINGLE_BLOB option, rather than SINGLE_CLOB and SINGLE_NCLOB, because only SINGLE_BLOB supports all Windows encoding conversions.
 
 ##### SINGLE_CLOB
+
 By reading *data_file* as ASCII, returns the contents as a single-row, single-column rowset of type **varchar(max)**, using the collation of the current database.
 
 ##### SINGLE_NCLOB
+
 By reading *data_file* as UNICODE, returns the contents as a single-row, single-column rowset of type **nvarchar(max)**, using the collation of the current database.
 
 ```sql
@@ -253,9 +265,10 @@ Specifies the code page of the data in the data file. CODEPAGE is relevant only
 |*code_page*|Indicates the source code page on which the character data in the data file is encoded; for example, 850.<br /><br /> **Important** Versions prior to [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)] do not support code page 65001 (UTF-8 encoding).|
 
 ##### FORMAT
+
 `FORMAT` **=** 'CSV'
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
-Specifies a comma separated values file compliant to the [RFC 4180](https://tools.ietf.org/html/rfc4180) standard.
+
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], specifies a comma separated values file compliant to the [RFC 4180](https://tools.ietf.org/html/rfc4180) standard.
 
 ```sql
 SELECT *
@@ -266,20 +279,21 @@ FROM OPENROWSET(BULK N'D:\XChange\test-csv.csv',
 ```
 
 ##### FORMATFILE
+
 `FORMATFILE` ='*format_file_path*'
 Specifies the full path of a format file. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports two types of format files: XML and non-XML.
 
 A format file is required to define column types in the result set. The only exception is when SINGLE_CLOB, SINGLE_BLOB, or SINGLE_NCLOB is specified; in which case, the format file is not required.
 
 For information about format files, see [Use a Format File to Bulk Import Data &#40;SQL Server&#41;](../../relational-databases/import-export/use-a-format-file-to-bulk-import-data-sql-server.md).
 
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
-Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1, the format_file_path can be in Azure Blob Storage. For examples, see [Examples of Bulk Access to Data in Azure Blob Storage](../../relational-databases/import-export/examples-of-bulk-access-to-data-in-azure-blob-storage.md).
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], the format_file_path can be in Azure Blob Storage. For examples, see [Examples of Bulk Access to Data in Azure Blob Storage](../../relational-databases/import-export/examples-of-bulk-access-to-data-in-azure-blob-storage.md).
 
 ##### FIELDQUOTE
+
 `FIELDQUOTE` **=** 'field_quote'
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
-Specifies a character that will be used as the quote character in the CSV file. If not specified, the quote character (") will be used as the quote character as defined in the [RFC 4180](https://tools.ietf.org/html/rfc4180) standard.
+
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], specifies a character that will be used as the quote character in the CSV file. If not specified, the quote character (") will be used as the quote character as defined in the [RFC 4180](https://tools.ietf.org/html/rfc4180) standard.
 
 ## Remarks
 
@@ -453,7 +467,7 @@ OPENROWSET (BULK N'D:\data.csv', FORMATFILE =
 
 ### G. Accessing data from a CSV file with a format file
 
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)].
 
 ```sql
 SELECT *
@@ -490,8 +504,7 @@ FROM OPENROWSET
 
 ### I. Accessing data from a file stored on Azure Blob storage
 
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CTP 1.1.
-The following example uses an external data source that points to a container in an Azure storage account and a database scoped credential created for a shared access signature.
+Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], the following example uses an external data source that points to a container in an Azure storage account and a database scoped credential created for a shared access signature.
 
 ```sql
 SELECT * FROM OPENROWSET(
@@ -569,7 +582,7 @@ SINGLE_CLOB
 
 ### L. Use OPENROWSET to access several parquet files using S3-compatible object storage
 
-**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] 
+**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later.
 
 The following example uses access several parquet files from different location, all stored on S3-compatible object storage: