Merge pull request #34508 from rwestMSFT/rw-0623-stored-procedures-009

System stored procedure refresh - phase 9

Author: AnnaMHuff

docs/relational-databases/system-stored-procedures/sp-purge-jobhistory-elastic-jobs-transact-sql.md

@@ -4,7 +4,7 @@ description: jobs.sp_purge_jobhistory removes the history records for a job crea
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest
-ms.date: 08/22/2024
+ms.date: 06/23/2025
 ms.service: azure-sql-database
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -74,7 +74,7 @@ Connect to the `job_database` and run the following command:
 --Connect to the job database specified when creating the job agent
 
 -- Delete history of a specific job's executions older than the specified date
-EXEC jobs.sp_purge_jobhistory
+EXECUTE jobs.sp_purge_jobhistory
     @job_name = 'ResultPoolsJob',
     @oldest_date = '2016-07-01 00:00:00';
 GO
@@ -90,7 +90,7 @@ Connect to the `job_database` and run the following command:
 --Connect to the job database specified when creating the job agent
 
 --Delete a job and all its history
-EXEC jobs.sp_delete_job @job_name = 'ResultsPoolsJob';
+EXECUTE jobs.sp_delete_job @job_name = 'ResultsPoolsJob';
 ```
 
 ## Related content

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

@@ -4,7 +4,7 @@ description: sp_purge_jobhistory removes the history records for a job in the SQ
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 08/21/2024
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -85,8 +85,7 @@ The following example removes the history for a job named `NightlyBackups`.
 USE msdb;
 GO
 
-EXEC dbo.sp_purge_jobhistory
-    @job_name = N'NightlyBackups';
+EXECUTE dbo.sp_purge_jobhistory @job_name = N'NightlyBackups';
 GO
 ```
 
@@ -100,7 +99,7 @@ The following example executes the procedure with no parameters to remove all hi
 USE msdb;
 GO
 
-EXEC dbo.sp_purge_jobhistory;
+EXECUTE dbo.sp_purge_jobhistory;
 GO
 ```
 

docs/relational-databases/system-stored-procedures/sp-query-store-clear-message-queues-transact-sql.md

@@ -4,7 +4,7 @@ description: "Clears all queued (non-persisted) Query Store messages pending for
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/07/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -22,7 +22,7 @@ monikerRange: ">=sql-server-ver16 || >=sql-server-linux-ver16"
 
 [!INCLUDE [sqlserver2022](../../includes/applies-to-version/sqlserver2022.md)]
 
-Clears all queued (non-persisted) Query Store messages pending for the replica against which the command is executed. `sp_query_store_clear_message_queues` is used when [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md) has been enabled.
+Clears all queued (non-persisted) Query Store messages pending for the replica against which the command is executed. `sp_query_store_clear_message_queues` is used when [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md) has been enabled.
 
 :::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)
 
@@ -50,13 +50,13 @@ Requires the ALTER permission on the database.
 The following example clears all queued (non-persisted) Query Store messages pending. The action applies to the replica against which the command is executed.
 
 ```sql
-EXEC sp_query_store_clear_message_queues;
+EXECUTE sp_query_store_clear_message_queues;
 ```
 
 ## Related content
 
 - [Monitor performance by using the Query Store](../performance/monitoring-performance-by-using-the-query-store.md)
-- [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md)
+- [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md)
 - [sys.database_query_store_internal_state (Transact-SQL)](../system-catalog-views/sys-database-query-store-internal-state-transact-sql.md)
 - [Query Store catalog views (Transact-SQL)](../system-catalog-views/query-store-catalog-views-transact-sql.md)
 - [Query Store stored procedures (Transact-SQL)](query-store-stored-procedures-transact-sql.md)

docs/relational-databases/system-stored-procedures/sp-query-store-flush-db-transact-sql.md

@@ -4,7 +4,7 @@ description: "Flushes the in-memory portion of the Query Store data to disk."
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/07/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -45,7 +45,7 @@ None.
 
 ## Remarks
 
-If [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md) is enabled, when `sys.sp_query_store_flush_db` is executed on a secondary replica, that secondary replica's cache is forced to flush to the cache on the primary replica. This can accelerate the Query Store cache data being synced to the primary replica, if the secondary replica cache flush is otherwise delayed under heavy workload.
+If [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md) is enabled, when `sys.sp_query_store_flush_db` is executed on a secondary replica, that secondary replica's cache is forced to flush to the cache on the primary replica. This can accelerate the Query Store cache data being synced to the primary replica, if the secondary replica cache flush is otherwise delayed under heavy workload.
 
 ## Permissions
 
@@ -56,13 +56,13 @@ Requires the ALTER permission on the database.
 The following example flushes the in-memory portion of the Query Store data to disk.
 
 ```sql
-EXEC sp_query_store_flush_db;
+EXECUTE sp_query_store_flush_db;
 ```
 
 ## Related content
 
 - [Monitor performance by using the Query Store](../performance/monitoring-performance-by-using-the-query-store.md)
-- [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md)
+- [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md)
 - [sp_query_store_force_plan (Transact-SQL)](sp-query-store-force-plan-transact-sql.md)
 - [sp_query_store_remove_query (Transact-SQL)](sp-query-store-remove-query-transact-sql.md)
 - [sp_query_store_unforce_plan (Transact-SQL)](sp-query-store-unforce-plan-transact-sql.md)

docs/relational-databases/system-stored-procedures/sp-query-store-force-plan-transact-sql.md

@@ -4,7 +4,7 @@ description: "Enables forcing a particular plan for a particular query in the Qu
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/19/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -59,7 +59,7 @@ Indicates whether optimized plan forcing should be disabled. *@disable_optimized
 
 #### [ @force_plan_scope = ] '*replica_group_id*'
 
-You can force plans on a secondary replica when [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md) is enabled. Execute `sp_query_store_force_plan` and `sp_query_store_unforce_plan` on the primary replica. Using the *@force_plan_scope* argument defaults to the local replica where the command is being executed, but you can specify a *replica_group_id* referencing the [sys.query_store_plan_forcing_locations](../system-catalog-views/sys-query-store-plan-forcing-locations-transact-sql.md) system catalog view.
+You can force plans on a secondary replica when [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md) is enabled. Execute `sp_query_store_force_plan` and `sp_query_store_unforce_plan` on the primary replica. Using the *@force_plan_scope* argument defaults to the local replica where the command is being executed, but you can specify a *replica_group_id* referencing the [sys.query_store_plan_forcing_locations](../system-catalog-views/sys-query-store-plan-forcing-locations-transact-sql.md) system catalog view.
 
 ## Return code values
 
@@ -81,33 +81,33 @@ The following example returns information about the queries in the Query Store.
 
 ```sql
 SELECT txt.query_text_id,
-    txt.query_sql_text,
-    pl.plan_id,
-    qry.*
+       txt.query_sql_text,
+       pl.plan_id,
+       qry.*
 FROM sys.query_store_plan AS pl
-INNER JOIN sys.query_store_query AS qry
-    ON pl.query_id = qry.query_id
-INNER JOIN sys.query_store_query_text AS txt
-    ON qry.query_text_id = txt.query_text_id;
+     INNER JOIN sys.query_store_query AS qry
+         ON pl.query_id = qry.query_id
+     INNER JOIN sys.query_store_query_text AS txt
+         ON qry.query_text_id = txt.query_text_id;
 ```
 
 After you identify the *query_id* and *plan_id* that you want to force, use the following example to force the query to use a plan.
 
 ```sql
-EXEC sp_query_store_force_plan
+EXECUTE sp_query_store_force_plan
     @query_id = 3,
     @plan_id = 3;
 ```
 
-Use [sys.query_store_plan_forcing_locations](../system-catalog-views/sys-query-store-plan-forcing-locations-transact-sql.md), joined with [sys.query_store_replicas](../system-catalog-views/sys-query-store-replicas.md), to retrieve [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md).
+Use [sys.query_store_plan_forcing_locations](../system-catalog-views/sys-query-store-plan-forcing-locations-transact-sql.md), joined with [sys.query_store_replicas](../system-catalog-views/sys-query-store-replicas.md), to retrieve [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md).
 
 ```sql
 SELECT query_plan
 FROM sys.query_store_plan AS qsp
-INNER JOIN sys.query_store_plan_forcing_locations AS pfl
-    ON pfl.query_id = qsp.query_id
-INNER JOIN sys.query_store_replicas AS qsr
-    ON qsr.replica_group_id = qsp.replica_group_id
+     INNER JOIN sys.query_store_plan_forcing_locations AS pfl
+         ON pfl.query_id = qsp.query_id
+     INNER JOIN sys.query_store_replicas AS qsr
+         ON qsr.replica_group_id = qsp.replica_group_id
 WHERE qsr.replica_name = 'yourSecondaryReplicaName';
 ```
 

docs/relational-databases/system-stored-procedures/sp-query-store-remove-plan-transact-sql.md

@@ -4,7 +4,7 @@ description: "Removes a single plan from the Query Store."
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/07/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -57,20 +57,20 @@ The following example returns information about the queries in the Query Store.
 
 ```sql
 SELECT txt.query_text_id,
-    txt.query_sql_text,
-    pl.plan_id,
-    qry.*
+       txt.query_sql_text,
+       pl.plan_id,
+       qry.*
 FROM sys.query_store_plan AS pl
-INNER JOIN sys.query_store_query AS qry
-    ON pl.query_id = qry.query_id
-INNER JOIN sys.query_store_query_text AS txt
-    ON qry.query_text_id = txt.query_text_id;
+     INNER JOIN sys.query_store_query AS qry
+         ON pl.query_id = qry.query_id
+     INNER JOIN sys.query_store_query_text AS txt
+         ON qry.query_text_id = txt.query_text_id;
 ```
 
 After you identify the *plan_id* that you want to delete, use the following example to delete a query plan.
 
 ```sql
-EXEC sp_query_store_remove_plan 3;
+EXECUTE sp_query_store_remove_plan 3;
 ```
 
 ## Related content

docs/relational-databases/system-stored-procedures/sp-query-store-remove-query-transact-sql.md

@@ -4,7 +4,7 @@ description: "sp_query_store_remove_query (Transact-SQL)"
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/07/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -57,20 +57,20 @@ The following example returns information about the queries in the Query Store.
 
 ```sql
 SELECT txt.query_text_id,
-    txt.query_sql_text,
-    pl.plan_id,
-    qry.*
+       txt.query_sql_text,
+       pl.plan_id,
+       qry.*
 FROM sys.query_store_plan AS pl
-INNER JOIN sys.query_store_query AS qry
-    ON pl.query_id = qry.query_id
-INNER JOIN sys.query_store_query_text AS txt
-    ON qry.query_text_id = txt.query_text_id;
+     INNER JOIN sys.query_store_query AS qry
+         ON pl.query_id = qry.query_id
+     INNER JOIN sys.query_store_query_text AS txt
+         ON qry.query_text_id = txt.query_text_id;
 ```
 
 After you identify the *query_id* that you want to delete, use the following example to delete the query.
 
 ```sql
-EXEC sp_query_store_remove_query 3;
+EXECUTE sp_query_store_remove_query 3;
 ```
 
 ## Related content

docs/relational-databases/system-stored-procedures/sp-query-store-reset-exec-stats-transact-sql.md

@@ -4,7 +4,7 @@ description: "Clears the runtime stats for a specific query plan from the Query
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/07/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -57,20 +57,20 @@ The following example returns information about the queries in the Query Store.
 
 ```sql
 SELECT txt.query_text_id,
-    txt.query_sql_text,
-    pl.plan_id,
-    qry.*
+       txt.query_sql_text,
+       pl.plan_id,
+       qry.*
 FROM sys.query_store_plan AS pl
-INNER JOIN sys.query_store_query AS qry
-    ON pl.query_id = qry.query_id
-INNER JOIN sys.query_store_query_text AS txt
-    ON qry.query_text_id = txt.query_text_id;
+     INNER JOIN sys.query_store_query AS qry
+         ON pl.query_id = qry.query_id
+     INNER JOIN sys.query_store_query_text AS txt
+         ON qry.query_text_id = txt.query_text_id;
 ```
 
 After you identify the *plan_id* that you want to clear the statistics, use the following example to delete the execution stats for a specific query plan. This example deletes the execution stats for plan number 3.
 
 ```sql
-EXEC sp_query_store_reset_exec_stats 3;
+EXECUTE sp_query_store_reset_exec_stats 3;
 ```
 
 ## Related content

docs/relational-databases/system-stored-procedures/sp-query-store-unforce-plan-transact-sql.md

@@ -4,7 +4,7 @@ description: "Enables unforcing a previously forced plan for a particular query
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/07/2025
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -52,7 +52,7 @@ The ID of the query plan that will no longer be enforced. *@plan_id* is **bigint
 
 #### [ @force_plan_scope = ] '*replica_group_id*'
 
-You can unforce plans on a secondary replica when [Query Store for secondary replicas](../performance/query-store-for-secondary-replicas.md) is enabled. Execute `sp_query_store_force_plan` and `sp_query_store_unforce_plan` on the primary replica. Using the *@force_plan_scope* argument defaults to the local replica where the command is being executed, but you can specify a *replica_group_id* referencing the [sys.query_store_plan_forcing_locations](../system-catalog-views/sys-query-store-plan-forcing-locations-transact-sql.md) system catalog view.
+You can unforce plans on a secondary replica when [Query Store for readable secondaries](../performance/query-store-for-secondary-replicas.md) is enabled. Execute `sp_query_store_force_plan` and `sp_query_store_unforce_plan` on the primary replica. Using the *@force_plan_scope* argument defaults to the local replica where the command is being executed, but you can specify a *replica_group_id* referencing the [sys.query_store_plan_forcing_locations](../system-catalog-views/sys-query-store-plan-forcing-locations-transact-sql.md) system catalog view.
 
 ## Return code values
 
@@ -68,20 +68,20 @@ The following example returns information about the queries in the Query Store.
 
 ```sql
 SELECT txt.query_text_id,
-    txt.query_sql_text,
-    pl.plan_id,
-    qry.*
+       txt.query_sql_text,
+       pl.plan_id,
+       qry.*
 FROM sys.query_store_plan AS pl
-INNER JOIN sys.query_store_query AS qry
-    ON pl.query_id = qry.query_id
-INNER JOIN sys.query_store_query_text AS txt
-    ON qry.query_text_id = txt.query_text_id;
+     INNER JOIN sys.query_store_query AS qry
+         ON pl.query_id = qry.query_id
+     INNER JOIN sys.query_store_query_text AS txt
+         ON qry.query_text_id = txt.query_text_id;
 ```
 
 After you identify the *query_id* and *plan_id* that you want to unforce, use the following example to unforce the plan.
 
 ```sql
-EXEC sp_query_store_unforce_plan 3, 3;
+EXECUTE sp_query_store_unforce_plan 3, 3;
 ```
 
 ## Related content

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

@@ -4,7 +4,7 @@ description: "Causes stored procedures, triggers, and user-defined functions to
 author: markingmyname
 ms.author: maghan
 ms.reviewer: wiassaf, randolphwest
-ms.date: 08/21/2024
+ms.date: 06/23/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -72,7 +72,8 @@ The following example causes stored procedures, triggers, and user-defined funct
 ```sql
 USE AdventureWorks2022;
 GO
-EXEC sp_recompile N'Sales.Customer';
+
+EXECUTE sp_recompile N'Sales.Customer';
 GO
 ```