Merge pull request #31639 from rwestMSFT/rw-0822-system-stored-procedures-0003

Latest bulk changes for system stored procedures

Author: v-shils

docs/relational-databases/system-stored-procedures/sp-wait-for-database-copy-sync-transact-sql.md

@@ -5,7 +5,7 @@ description: "sp_wait_for_database_copy_sync is scoped to an active geo-replicat
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 04/27/2023
+ms.date: 08/21/2024
 ms.service: azure-sql-database
 ms.topic: "reference"
 f1_keywords:
@@ -74,5 +74,5 @@ GO
 ## Related content
 
 - [sys.dm_continuous_copy_status (Azure SQL Database)](../system-dynamic-management-views/sys-dm-continuous-copy-status-azure-sql-database.md)
-- [Geo-Replication Dynamic Management Views (DMVs) and Functions (Azure SQL Database)](../system-dynamic-management-views/geo-replication-dynamic-management-views-and-functions-azure-sql-database.md)
+- [Geo-Replication Dynamic Management Views and Functions (Azure SQL Database)](../system-dynamic-management-views/geo-replication-dynamic-management-views-and-functions-azure-sql-database.md)
 - [sys.dm_geo_replication_link_status](../system-dynamic-management-views/sys-dm-geo-replication-link-status-azure-sql-database.md)

docs/relational-databases/system-stored-procedures/sp-who-transact-sql.md

@@ -4,7 +4,7 @@ description: Provides information about current users, sessions, and processes i
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: randolphwest
-ms.date: 07/06/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -69,9 +69,9 @@ With parallel processing, subthreads are created for the specific session ID. Th
 
 ## Remarks
 
-A blocking process, which may have an exclusive lock, is one that is holding resources that another process needs.
+A blocking process, which might have an exclusive lock, is one that is holding resources that another process needs.
 
-All orphaned distributed transactions are assigned the session ID value of `-2`. Orphaned distributed transactions are distributed transactions that aren't associated with any session ID. For more information, see [Use Marked Transactions to Recover Related Databases Consistently (Full Recovery Model)](../backup-restore/use-marked-transactions-to-recover-related-databases-consistently.md).
+All orphaned distributed transactions are assigned the session ID value of `-2`. Orphaned distributed transactions are distributed transactions that aren't associated with any session ID. For more information, see [Use Marked Transactions to Recover Related Databases Consistently](../backup-restore/use-marked-transactions-to-recover-related-databases-consistently.md).
 
 Query the `is_user_process` column of `sys.dm_exec_sessions` to separate system processes from user processes.
 

docs/relational-databases/system-stored-procedures/sp-xml-preparedocument-transact-sql.md

@@ -4,7 +4,7 @@ description: "Reads the XML text provided as input, parses the text by using the
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 06/26/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -31,7 +31,7 @@ For backward compatibility, `sp_xml_preparedocument` collapses the CR (`char(13)
 > [!NOTE]  
 > The XML parser invoked by `sp_xml_preparedocument` can parse internal DTDs and entity declarations. Because maliciously constructed DTDs and entity declarations can be used to perform a denial of service attack, we strongly recommend that users not directly pass XML documents from untrusted sources to `sp_xml_preparedocument`.  
 >  
-> To mitigate recursive entity expansion attacks, `sp_xml_preparedocument` limits to 10,000 the number of entities that can be expanded underneath a single entity at the top level of a document. The limit does not apply to character or numeric entities. This limit allows documents with many entity references to be stored, but prevents any one entity from being recursively expanded in a chain longer than 10,000 expansions.
+> To mitigate recursive entity expansion attacks, `sp_xml_preparedocument` limits to 10,000 the number of entities that can be expanded underneath a single entity at the top level of a document. The limit doesn't apply to character or numeric entities. This limit allows documents with many entity references to be stored, but prevents any one entity from being recursively expanded in a chain longer than 10,000 expansions.
 
 `sp_xml_preparedocument` limits the number of elements that can be open at one time to 256.
 
@@ -54,10 +54,10 @@ The handle to the newly created document. *hdoc* is an integer.
 
 #### [ *xmltext* ]
 
-The original XML document. The MSXML parser parses this XML document. *xmltext* is a text parameter: **char**, **nchar**, **varchar**, **nvarchar**, **text**, **ntext** or **xml**. The default value is NULL, in which case an internal representation of an empty XML document is created.
+The original XML document. The MSXML parser parses this XML document. *xmltext* is a text parameter: **char**, **nchar**, **varchar**, **nvarchar**, **text**, **ntext** or **xml**. The default value is `NULL`, in which case an internal representation of an empty XML document is created.
 
 > [!NOTE]  
-> `sp_xml_preparedocument` can only process text or untyped XML. If an instance value to be used as input is already typed XML, first cast it to a new untyped XML instance or as a string and then pass that value as input. For more information, see [Compare Typed XML to Untyped XML](../xml/compare-typed-xml-to-untyped-xml.md).
+> `sp_xml_preparedocument` can only process text or untyped XML. If an instance value to be used as input is already typed XML, first cast it to a new untyped XML instance or as a string and then pass that value as input. For more information, see [Compare typed XML to untyped XML](../xml/compare-typed-xml-to-untyped-xml.md).
 
 #### [ *xpath_namespaces* ]
 
@@ -154,9 +154,9 @@ EXEC sp_xml_preparedocument @hdoc OUTPUT, @doc, '<ROOT xmlns:xyz="urn:MyNamespac
 
 ## Related content
 
-- [XML Stored Procedures(Transact-SQL)](xml-stored-procedures-transact-sql.md)
-- [System Stored Procedures(Transact-SQL)](system-stored-procedures-transact-sql.md)
-- [OPENXML(Transact-SQL)](../../t-sql/functions/openxml-transact-sql.md)
+- [XML stored procedures (Transact-SQL)](xml-stored-procedures-transact-sql.md)
+- [System stored procedures (Transact-SQL)](system-stored-procedures-transact-sql.md)
+- [OPENXML (Transact-SQL)](../../t-sql/functions/openxml-transact-sql.md)
 - [sys.dm_exec_xml_handles (Transact-SQL)](../system-dynamic-management-views/sys-dm-exec-xml-handles-transact-sql.md)
 - [sp_xml_removedocument (Transact-SQL)](sp-xml-removedocument-transact-sql.md)
 - [nodes() Method (xml Data Type)](../../t-sql/xml/nodes-method-xml-data-type.md)

docs/relational-databases/system-stored-procedures/sp-xp-cmdshell-proxy-account-transact-sql.md

@@ -4,7 +4,7 @@ description: Creates a proxy credential for xp_cmdshell.
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 07/06/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -38,31 +38,31 @@ sp_xp_cmdshell_proxy_account [ NULL | { 'account_name' , 'password' } ]
 
 ## Arguments
 
-- **NULL**
+#### NULL
 
-  Specifies that the proxy credential should be deleted.
+Specifies that the proxy credential should be deleted.
 
-- **'*account_name*'**
+#### '*account_name*'
 
-  Specifies the Windows account to be the proxy.
+Specifies the Windows account to be the proxy.
 
-- **'*password*'**
+#### '*password*'
 
-  Specifies the password of the Windows account.
+Specifies the password of the Windows account.
 
 ## Return code values
 
 `0` (success) or `1` (failure).
 
 ## Remarks
 
-The proxy credential is called **##xp_cmdshell_proxy_account##**.
+The proxy credential is called `##xp_cmdshell_proxy_account##`.
 
-When it is executed using the NULL option, `sp_xp_cmdshell_proxy_account` deletes the proxy credential.
+When it's executed using the `NULL` option, `sp_xp_cmdshell_proxy_account` deletes the proxy credential.
 
 ## Permissions
 
-Requires CONTROL SERVER permission.
+Requires `CONTROL SERVER` permission.
 
 ## Examples
 

docs/relational-databases/system-stored-procedures/sql-data-warehouse-stored-procedures.md

@@ -4,7 +4,7 @@ description: "Azure Synapse Analytics stored procedures"
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest
-ms.date: 05/24/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.topic: "reference"
 dev_langs:
@@ -31,7 +31,7 @@ monikerRange: "=azure-sqldw-latest || =fabric"
 - [sp_special_columns_100 (Azure Synapse Analytics)](sp-special-columns-100-sql-data-warehouse.md)
 
 > [!NOTE]  
-> Some additional system stored procedures are used only within an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] or through client APIs and aren't intended for general customer use. These procedures are listed at [System stored procedures (Transact-SQL)](./system-stored-procedures-transact-sql.md). These procedures are subject to change and compatibility isn't guaranteed. All procedures on the list aren't available in [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)].
+> Some additional system stored procedures are used only within an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] or through client APIs and aren't intended for general customer use. These procedures are listed at [System stored procedures](system-stored-procedures-transact-sql.md). These procedures are subject to change and compatibility isn't guaranteed. All procedures on the list aren't available in [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)].
 
 ## Related content
 

docs/relational-databases/system-stored-procedures/sql-server-profiler-stored-procedures-transact-sql.md

@@ -4,7 +4,7 @@ description: "SQL Server Profiler stored procedures (Transact-SQL)"
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 05/24/2023
+ms.date: 08/22/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -38,7 +38,7 @@ dev_langs:
     :::column-end:::
 :::row-end:::
 
-For an example of using trace stored procedures, see [Create a Trace (Transact-SQL)](../sql-trace/create-a-trace-transact-sql.md).
+For an example of using trace stored procedures, see [Create a Trace](../sql-trace/create-a-trace-transact-sql.md).
 
 ## Related content
 

docs/relational-databases/system-stored-procedures/sys-sp-add-trusted-assembly-transact-sql.md

@@ -4,7 +4,7 @@ description: Adds an assembly to the list of trusted assemblies for the server.
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: randolphwest
-ms.date: 07/06/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -44,7 +44,7 @@ This procedure adds an assembly to [sys.trusted_assemblies](../system-catalog-vi
 
 #### [ @hash = ] '*value*'
 
-The SHA2_512 hash value of the assembly to add to the list of trusted assemblies for the server. Trusted assemblies may load when [CLR strict security](../../database-engine/configure-windows/clr-strict-security.md) is enabled, even if the assembly is unsigned or the database isn't marked as trustworthy.
+The SHA2_512 hash value of the assembly to add to the list of trusted assemblies for the server. Trusted assemblies might load when [Server configuration: clr strict security](../../database-engine/configure-windows/clr-strict-security.md) is enabled, even if the assembly is unsigned or the database isn't marked as trustworthy.
 
 #### [ @description = ] '*description*'
 
@@ -66,9 +66,9 @@ EXEC sp_add_trusted_assembly
 
 ## Related content
 
-- [sys.sp_drop_trusted_assembly](sys-sp-drop-trusted-assembly-transact-sql.md)
-- [sys.trusted_assemblies](../system-catalog-views/sys-trusted-assemblies-transact-sql.md)
+- [sys.sp_drop_trusted_assembly (Transact-SQL)](sys-sp-drop-trusted-assembly-transact-sql.md)
+- [sys.trusted_assemblies (Transact-SQL)](../system-catalog-views/sys-trusted-assemblies-transact-sql.md)
 - [CREATE ASSEMBLY (Transact-SQL)](../../t-sql/statements/create-assembly-transact-sql.md)
-- [CLR strict security](../../database-engine/configure-windows/clr-strict-security.md)
-- [sys.assemblies](../system-catalog-views/sys-assemblies-transact-sql.md)
-- [sys.dm_clr_loaded_assemblies](../system-dynamic-management-views/sys-dm-clr-loaded-assemblies-transact-sql.md)
+- [Server configuration: clr strict security](../../database-engine/configure-windows/clr-strict-security.md)
+- [sys.assemblies (Transact-SQL)](../system-catalog-views/sys-assemblies-transact-sql.md)
+- [sys.dm_clr_loaded_assemblies (Transact-SQL)](../system-dynamic-management-views/sys-dm-clr-loaded-assemblies-transact-sql.md)

docs/relational-databases/system-stored-procedures/sys-sp-cdc-add-job-transact-sql.md

@@ -4,7 +4,7 @@ description: "Creates a change data capture cleanup or capture job in the curren
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 06/13/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -44,7 +44,7 @@ sys.sp_cdc_add_job [ @job_type = ] N'job_type'
 
 #### [ @job_type = ] N'*job_type*'
 
-Type of job to add. *@job_type* is **nvarchar(20)** and can't be NULL. Valid inputs are `capture` and `cleanup`.
+Type of job to add. *@job_type* is **nvarchar(20)** and can't be `NULL`. Valid inputs are `capture` and `cleanup`.
 
 #### [ @start_job = ] *start_job*
 
@@ -66,7 +66,7 @@ Maximum number of scan cycles to execute in order to extract all rows from the l
 
 Indicates whether the capture job is to run continuously (`1`), or run only once (`0`). *@continuous* is **bit** with a default of `1`.
 
-- When *@continuous* is `1`, the [sp_cdc_scan](sys-sp-cdc-scan-transact-sql.md) job scans the log and processes up to (`@maxtrans * @maxscans`) transactions. It then waits the number of seconds specified in *@pollinginterval* before beginning the next log scan.
+- When *@continuous* is `1`, the [sys.sp_cdc_scan](sys-sp-cdc-scan-transact-sql.md) job scans the log and processes up to (`@maxtrans * @maxscans`) transactions. It then waits the number of seconds specified in *@pollinginterval* before beginning the next log scan.
 
 - When *@continuous* is `0`, the `sp_cdc_scan` job executes up to *@maxscans* scans of the log, processing up to *@maxtrans* transaction during each scan, and then exits.
 
@@ -104,7 +104,7 @@ Because the cleanup and capture jobs are created by default, this stored procedu
 
 The name of the job is `cdc.<database_name>_cleanup` or `cdc.<database_name>_capture`, where `<database_name>` is the name of the current database. If a job with the same name already exists, the name is appended with a period (`.`) followed by a unique identifier, for example: `cdc.AdventureWorks_capture.A1ACBDED-13FC-428C-8302-10100EF74F52`.
 
-To view the current configuration of a cleanup or capture job, use [sp_cdc_help_jobs](sys-sp-cdc-help-jobs-transact-sql.md). To change the configuration of a job, use [sp_cdc_change_job](sys-sp-cdc-change-job-transact-sql.md).
+To view the current configuration of a cleanup or capture job, use [sys.sp_cdc_help_jobs](sys-sp-cdc-help-jobs-transact-sql.md). To change the configuration of a job, use [sys.sp_cdc_change_job](sys-sp-cdc-change-job-transact-sql.md).
 
 ## Permissions
 

docs/relational-databases/system-stored-procedures/sys-sp-cdc-change-job-transact-sql.md

@@ -4,7 +4,7 @@ description: "Modifies the configuration of a change data capture cleanup or cap
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 06/13/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -22,7 +22,7 @@ dev_langs:
 
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-Modifies the configuration of a change data capture cleanup or capture job in the current database. To view the current configuration of a job, query the [dbo.cdc_jobs](../system-tables/dbo-cdc-jobs-transact-sql.md) table, or use [sp_cdc_help_jobs](sys-sp-cdc-help-jobs-transact-sql.md).
+Modifies the configuration of a change data capture cleanup or capture job in the current database. To view the current configuration of a job, query the [dbo.cdc_jobs](../system-tables/dbo-cdc-jobs-transact-sql.md) table, or use [sys.sp_cdc_help_jobs](sys-sp-cdc-help-jobs-transact-sql.md).
 
 :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
 
@@ -61,13 +61,13 @@ Maximum number of scan cycles to execute in order to extract all rows from the l
 
 Indicates whether the capture job is to run continuously (`1`), or run only once (`0`). *@continuous* is **bit**, with a default of `NULL`, which indicates no change for this parameter.
 
-- When *@continuous* is `1`, the [sp_cdc_scan](sys-sp-cdc-scan-transact-sql.md) job scans the log and processes up to (`@maxtrans * @maxscans`) transactions. It then waits the number of seconds specified in *@pollinginterval* before beginning the next log scan.
+- When *@continuous* is `1`, the [sys.sp_cdc_scan](sys-sp-cdc-scan-transact-sql.md) job scans the log and processes up to (`@maxtrans * @maxscans`) transactions. It then waits the number of seconds specified in *@pollinginterval* before beginning the next log scan.
 
 - When *@continuous* is `0`, the `sp_cdc_scan` job executes up to *@maxscans* scans of the log, processing up to *@maxtrans* transactions during each scan, and then exits.
 
 - If *@continuous* is changed from `1` to `0`, *@pollinginterval* is automatically set to `0`. A value specified for *@pollinginterval* other than `0` is ignored.
 
-- If *@continuous* is omitted or explicitly set to NULL and *@pollinginterval* is explicitly set to a value greater than `0`, *@continuous* is automatically set to `1`.
+- If *@continuous* is omitted or explicitly set to `NULL` and *@pollinginterval* is explicitly set to a value greater than `0`, *@continuous* is automatically set to `1`.
 
 *@continuous* is valid only for capture jobs.
 
@@ -97,11 +97,11 @@ None.
 
 ## Remarks
 
-If a parameter is omitted, the associated value in the [dbo.cdc_jobs](../system-tables/dbo-cdc-jobs-transact-sql.md) table isn't updated. A parameter set explicitly to NULL is treated as though the parameter is omitted.
+If a parameter is omitted, the associated value in the [dbo.cdc_jobs](../system-tables/dbo-cdc-jobs-transact-sql.md) table isn't updated. A parameter set explicitly to `NULL` is treated as though the parameter is omitted.
 
 Specifying a parameter that is invalid for the job type causes the statement to fail.
 
-Changes to a job don't take effect until the job is stopped by using [sp_cdc_stop_job](sys-sp-cdc-stop-job-transact-sql.md) and restarted by using [sp_cdc_start_job](sys-sp-cdc-start-job-transact-sql.md).
+Changes to a job don't take effect until the job is stopped by using [sys.sp_cdc_stop_job](sys-sp-cdc-stop-job-transact-sql.md) and restarted by using [sys.sp_cdc_start_job](sys-sp-cdc-start-job-transact-sql.md).
 
 ## Permissions
 

docs/relational-databases/system-stored-procedures/sys-sp-cdc-drop-job-transact-sql.md

@@ -4,7 +4,7 @@ description: "Removes a change data capture cleanup or capture job for the curre
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 06/13/2023
+ms.date: 08/21/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -37,7 +37,7 @@ sys.sp_cdc_drop_job [ [ @job_type = ] N'job_type' ]
 
 #### [ @job_type = ] N'*job_type*'
 
-Type of job to remove. *job_type* is **nvarchar(20)** and can't be NULL. Valid inputs are `capture` and `cleanup`.
+Type of job to remove. *job_type* is **nvarchar(20)** and can't be `NULL`. Valid inputs are `capture` and `cleanup`.
 
 ## Return code values