System stored procedures: Refresh batch 035

Author: rwestMSFT

docs/includes/big-data-clusters-master-instance-ha-endpoint-requirement.md

@@ -6,6 +6,6 @@ ms.service: sql
 ms.topic: include
 ---
 
-Certain operations, including configuring server (instance level) settings, or manually adding a database to an availability group, require a connection to the SQL Server Instance. Operations like `sp_configure`, `RESTORE DATABASE`, or any DDL command in a database belonging to an availability group require a connection to the SQL Server instance. By default, a big data cluster does not include an endpoint that enables a connection to the instance. You must expose this endpoint manually.
+Certain operations, including configuring server (instance level) settings, or manually adding a database to an availability group, require a connection to the SQL Server instance. Operations like `sp_configure`, `RESTORE DATABASE`, or any DDL command in a database belonging to an availability group require a connection to the SQL Server instance. By default, a big data cluster does not include an endpoint that enables a connection to the instance. You must expose this endpoint manually.
 
 For instructions, see [Connect to databases on the primary replica](../big-data-cluster/deployment-high-availability.md#instance-connect).

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

@@ -23,7 +23,9 @@ dev_langs:
 
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-Defines the name of the local instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. When the computer hosting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is renamed, use `sp_addserver` to inform the instance of the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)] of the new computer name. This procedure must be executed on all instances of the [!INCLUDE [ssDE](../../includes/ssde-md.md)] hosted on the computer. The instance name of the [!INCLUDE [ssDE](../../includes/ssde-md.md)] can't be changed. To change the instance name of a named instance, install a new instance with the desired name, detach the database files from old instance, attach the databases to the new instance, and drop the old instance. Alternatively, you can create a client alias name on the client computer, redirecting the connection to different server and instance name or **server:port** combination without changing the name of the instance on the server computer.
+Defines the name of the local instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. When the computer hosting [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is renamed, use `sp_addserver` to inform the instance of the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)] of the new computer name. This procedure must be executed on all instances of the [!INCLUDE [ssDE](../../includes/ssde-md.md)] hosted on the computer.
+
+The instance name of the [!INCLUDE [ssDE](../../includes/ssde-md.md)] can't be changed. To change the instance name of a named instance, install a new instance with the desired name, detach the database files from old instance, attach the databases to the new instance, and drop the old instance. Alternatively, you can create a client alias name on the client computer, redirecting the connection to different server and instance name or `<server>:<port>` combination without changing the name of the instance on the server computer.
 
 :::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)
 
@@ -91,3 +93,4 @@ EXEC sp_addserver 'ACCOUNTS', 'local';
 - [sp_helpserver (Transact-SQL)](sp-helpserver-transact-sql.md)
 - [System stored procedures (Transact-SQL)](system-stored-procedures-transact-sql.md)
 - [Security stored procedures (Transact-SQL)](security-stored-procedures-transact-sql.md)
+- [Connect to the Database Engine](../../sql-server/connect-to-database-engine.md)

docs/relational-databases/system-stored-procedures/sp-can-tlog-be-applied-transact-sql.md

@@ -1,9 +1,10 @@
 ---
 title: "sp_can_tlog_be_applied (Transact-SQL)"
-description: "sp_can_tlog_be_applied (Transact-SQL)"
+description: Verifies whether a transaction log backup can be applied to a SQL Server database.
 author: markingmyname
 ms.author: maghan
-ms.date: "03/14/2017"
+ms.reviewer: randolphwest
+ms.date: 07/05/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -16,57 +17,70 @@ dev_langs:
   - "TSQL"
 ---
 # sp_can_tlog_be_applied (Transact-SQL)
+
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-  Verifies whether a transaction log backup can be applied to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database. **sp_can_tlog_be_applied** requires that the database be in the Restoring state.  
-  
- :::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)  
-  
-## Syntax  
-  
-```  
-  
-sp_can_tlog_be_applied [ @backup_file_name = ] 'backup_file_name'   
-        , [ @database_name = ] 'database_name'   
-        , [ @result = ] result OUTPUT  
-```  
-  
-## Arguments  
-`[ @backup_file_name = ] 'backup_file_name'`
- Is the name of a backup file. *backup_file_name* is **nvarchar(128)**.  
-  
-`[ @database_name = ] 'database_name'`
- Is the name of the database. *database_name* is **sysname**.  
-  
-`[ @result = ] _result_ OUTPUT`
- Indicates whether the transaction log can be applied to the database. *result* is **bit**.  
-  
- 1 = The log can be applies  
-  
- 0= The log cannot be applied.  
-  
-## Return Code Values  
- 0 (success) or 1 (failure)  
-  
-## Permissions  
- Only members of the **sysadmin** fixed server role can execute **sp_can_tlog_be_applied**.  
-  
-## Examples  
- The following example declares a local variable, `@MyBitVar`, to store the result.  
-  
-```  
-USE master;  
-GO  
-DECLARE @MyBitVar BIT;  
-EXEC sp_can_tlog_be_applied  
-     @backup_file_name =   
-N'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Backup\AdventureWorks2022.bak',  
-     @database_name = N'AdventureWorks2022',  
-     @result = @MyBitVar OUTPUT;  
-GO  
-```  
-  
-## See Also  
- [System Stored Procedures (Transact-SQL)](../../relational-databases/system-stored-procedures/system-stored-procedures-transact-sql.md)  
-  
-  
+Verifies whether a transaction log backup can be applied to a [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] database. `sp_can_tlog_be_applied` requires that the database is in the *restoring* state.
+
+:::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)
+
+## Syntax
+
+```syntaxsql
+sp_can_tlog_be_applied
+    [ @backup_file_name = ] N'backup_file_name'
+    , [ @database_name = ] N'database_name'
+    [ , [ @result = ] result OUTPUT ]
+    [ , [ @verbose = ] verbose ]
+[ ; ]
+```
+
+## Arguments
+
+#### [ @backup_file_name = ] N'*backup_file_name*'
+
+The name of a backup file. *@backup_file_name* is **nvarchar(500)**, with no default.
+
+#### [ @database_name = ] N'*database_name*'
+
+The name of the database. *@database_name* is **sysname**, with no default.
+
+#### [ @result = ] *result* OUTPUT
+
+Indicates whether the transaction log can be applied to the database. *@result* is an OUTPUT parameter of type **bit**.
+
+- `1` = The log can be applies
+- `0` = The log can't be applied.
+
+#### [ @verbose = ] *verbose*
+
+[!INCLUDE [ssinternalonly-md](../../includes/ssinternalonly-md.md)]
+
+## Return code values
+
+`0` (success) or `1` (failure).
+
+## Permissions
+
+Only members of the **sysadmin** fixed server role can execute `sp_can_tlog_be_applied`.
+
+## Examples
+
+The following example declares a local variable, `@MyBitVar`, to store the result.
+
+```sql
+USE master;
+GO
+
+DECLARE @MyBitVar BIT;
+
+EXEC sp_can_tlog_be_applied
+    @backup_file_name = N'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Backup\AdventureWorks2022.bak',
+    @database_name = N'AdventureWorks2022',
+    @result = @MyBitVar OUTPUT;
+GO
+```
+
+## Related content
+
+- [System stored procedures (Transact-SQL)](system-stored-procedures-transact-sql.md)

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

@@ -1,9 +1,10 @@
 ---
 title: "sp_catalogs (Transact-SQL)"
-description: "sp_catalogs (Transact-SQL)"
+description: sp_catalogs returns the list of catalogs in the specified linked server.
 author: markingmyname
 ms.author: maghan
-ms.date: "03/14/2017"
+ms.reviewer: randolphwest
+ms.date: 07/05/2024
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -16,55 +17,59 @@ dev_langs:
   - "TSQL"
 ---
 # sp_catalogs (Transact-SQL)
+
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-  Returns the list of catalogs in the specified linked server. This is equivalent to databases in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.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)  
-  
-## Syntax  
-  
-```  
-  
-sp_catalogs [ @server_name = ] 'linked_svr'  
-```  
-  
-## Arguments  
-`[ @server_name = ] 'linked_svr'`
- Is the name of a linked server. *linked_svr* is **sysname**, with no default.  
-  
-## Result Sets  
-  
-|Column name|Data type|Description|  
-|-----------------|---------------|-----------------|  
-|**Catalog_name**|**nvarchar(**128**)**|Name of the catalog|  
-|**Description**|**nvarchar(**4000**)**|Description of the catalog|  
-  
-## Permissions  
- Requires SELECT permission on the schema.  
-  
-## Examples  
- The following example returns catalog information for the linked server named `OLE DB ODBC Linked Server #3`.  
-  
+Returns the list of catalogs in the specified linked server. This is equivalent to databases in [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.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)
+
+## Syntax
+
+```syntaxsql
+sp_catalogs [ @server_name = ] N'server_name'
+[ ; ]
+```
+
+## Arguments
+
+#### [ @server_name = ] N'*server_name*'
+
+The name of a linked server. *@server_name* is **sysname**, with no default.
+
+## Result set
+
+| Column name | Data type | Description |
+| --- | --- | --- |
+| `CATALOG_NAME` | **nvarchar(128)** | Name of the catalog |
+| `DESCRIPTION` | **nvarchar(4000)** | Description of the catalog |
+
+## Permissions
+
+Requires `SELECT` permission on the schema.
+
+## Examples
+
+The following example returns catalog information for the linked server named `OLE DB ODBC Linked Server #3`.
+
 > [!NOTE]  
->  For **sp_catalogs** to provide useful information, the `OLE DB ODBC Linked Server #3` must already exist.  
-  
-```  
-USE master;  
-GO  
-EXEC sp_catalogs 'OLE DB ODBC Linked Server #3';  
-```  
-  
-## See Also  
- [sp_addlinkedserver (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-addlinkedserver-transact-sql.md)   
- [sp_columns_ex (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-columns-ex-transact-sql.md)   
- [sp_column_privileges (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-column-privileges-transact-sql.md)   
- [sp_foreignkeys (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-foreignkeys-transact-sql.md)   
- [sp_indexes (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-indexes-transact-sql.md)   
- [sp_linkedservers (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-linkedservers-transact-sql.md)   
- [sp_primarykeys (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-primarykeys-transact-sql.md)   
- [sp_tables_ex (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-tables-ex-transact-sql.md)   
- [sp_table_privileges (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-table-privileges-transact-sql.md)   
- [System Stored Procedures (Transact-SQL)](../../relational-databases/system-stored-procedures/system-stored-procedures-transact-sql.md)  
-  
-  
+> For `sp_catalogs` to provide useful information, the `OLE DB ODBC Linked Server #3` must already exist.
+
+```sql
+USE master;
+GO
+EXEC sp_catalogs 'OLE DB ODBC Linked Server #3';
+```
+
+## Related content
+
+- [sp_addlinkedserver (Transact-SQL)](sp-addlinkedserver-transact-sql.md)
+- [sp_columns_ex (Transact-SQL)](sp-columns-ex-transact-sql.md)
+- [sp_column_privileges (Transact-SQL)](sp-column-privileges-transact-sql.md)
+- [sp_foreignkeys (Transact-SQL)](sp-foreignkeys-transact-sql.md)
+- [sp_indexes (Transact-SQL)](sp-indexes-transact-sql.md)
+- [sp_linkedservers (Transact-SQL)](sp-linkedservers-transact-sql.md)
+- [sp_primarykeys (Transact-SQL)](sp-primarykeys-transact-sql.md)
+- [sp_tables_ex (Transact-SQL)](sp-tables-ex-transact-sql.md)
+- [sp_table_privileges (Transact-SQL)](sp-table-privileges-transact-sql.md)
+- [System stored procedures (Transact-SQL)](system-stored-procedures-transact-sql.md)