TSQL -> T-SQL or Transact-SQL

Author: rwestMSFT

azure-sql/migration-guides/managed-instance/sql-server-to-sql-managed-instance-assessment-rules.md

@@ -528,7 +528,7 @@ More information: [Discontinued Database Engine Functionality in SQL Server](/pr
 
 
 **Description**   
-It is a job step that runs TSQL scripts at scheduled time. TSQL job step includes unsupported commands which are not supported in Azure SQL Managed Instance.
+It is a job step that runs Transact-SQL scripts at scheduled time. TSQL job step includes unsupported commands which are not supported in Azure SQL Managed Instance.
 
 
 

docs/azure-data-studio/deploy-azure-sql-edge.md

@@ -35,7 +35,7 @@ The following scenarios are supported by the deployment wizard in Azure Data Stu
 > [!NOTE]
 > Azure SQL Edge deployment (preview) is available through the extension "Azure SQL Edge Deployment Extension" while these features are in preview. To make the features available to you, please install the extension in Azure Data Studio.
 
-To begin a deployment in Azure Data Studio, open the menu in the **Connections** view and select the **New Deployment...** option.  For all Azure SQL Edge scenarios, select **Azure SQL Edge** on the following screen and the desired scenario from the **Deployment target** drop-down. The deployment wizard generates a TSQL notebook that can be executed to complete the deployment. It should be noted that connection information, including the SQL admin password, is contained in the notebook by default.
+To begin a deployment in Azure Data Studio, open the menu in the **Connections** view and select the **New Deployment...** option.  For all Azure SQL Edge scenarios, select **Azure SQL Edge** on the following screen and the desired scenario from the **Deployment target** drop-down. The deployment wizard generates a Transact-SQL notebook that can be executed to complete the deployment. It should be noted that connection information, including the SQL admin password, is contained in the notebook by default.
 
 ![deployment overview](media/deploy-azure-sql-edge/deploy-overview.png)
 

docs/big-data-cluster/big-data-cluster-faq.yml

@@ -204,7 +204,7 @@ sections:
           Yes, you can connect to various Big Data Cluster services using integrated authentication (with Active Directory). For more information, see [Deploy SQL Server Big Data Cluster in Active Directory mode](active-directory-deploy.md). Also see [Security concepts for Big Data Clusters](concept-security.md).
       - question: How can I add new users for various services within Big Data Cluster?
         answer: |
-          In basic authentication mode (username/password), there is no support for adding multiple users for controller or Knox gateway/HDFS endpoints. The only user supported for these endpoints is root. For SQL Server, you can add users using TSQL as you would for any other SQL Server instance. 
+          In basic authentication mode (username/password), there is no support for adding multiple users for controller or Knox gateway/HDFS endpoints. The only user supported for these endpoints is root. For SQL Server, you can add users using Transact-SQL as you would for any other SQL Server instance. 
           If you deploy Big Data Cluster with AD auth for its endpoints, multiple users are supported. See here for details on how to configure the AD groups at deployment time. For more information, see [Deploy SQL Server Big Data Cluster in Active Directory mode](active-directory-deploy.md).
       - question: For Big Data Cluster to pull the latest container images, is there an outbound IP range I can restrict?
         answer: |

docs/big-data-cluster/change-azdata-password.md

@@ -80,7 +80,7 @@ If the cluster operates in non-Active Directory mode, update the Apache Knox Gat
 
 1. Connect to the master SQL endpoint with any administrator user.
 
-1. To change the password for the login credentials that you defined during deployment in the parameter `AZDATA_USERNAME`, run the following TSQL command:
+1. To change the password for the login credentials that you defined during deployment in the parameter `AZDATA_USERNAME`, run the following Transact-SQL command:
 
    ```sql
    ALTER LOGIN <AZDATA_USERNAME> WITH PASSWORD = 'newPassword'

docs/big-data-cluster/manage-user-access.md

@@ -36,7 +36,7 @@ To grant additional Active Directory groups *bdcUser* permissions without alteri
 
 1. Connect to the master SQL endpoint by using your favorite SQL client. Use any administrator login (for example, `AZDATA_USERNAME`, which was provided during deployment). Alternatively, it could be any Active Directory account that belongs to the Active Directory group that's provided as `clusterAdmins` in the security configuration.
 
-1. To create a login for the Active Directory user or group, run the following TSQL command:
+1. To create a login for the Active Directory user or group, run the following Transact-SQL command:
 
    ```sql
    CREATE LOGIN [<domain>\<principal>] FROM WINDOWS;

docs/connect/oledb/ole-db-interfaces/ibcpsession2-bcpsetbulkmode.md

@@ -325,7 +325,7 @@ BOOL BCPSetBulkMode(LPWSTR pszServer, LPTSTR pszQureryOut, char BCPType, LPWSTR
                return false;  
             }  
 
-            // set queryout TSQL statement  
+            // set queryout T-SQL statement  
             hr = g_pIBcpSession->BCPControl(BCP_OPTION_HINTS, pszQureryOut);  
             if (FAILED(hr)) {  
                printf("BCPControl failed\n");  

docs/linux/sql-server-linux-replication-tutorial-tsql.md

@@ -17,7 +17,7 @@ monikerRange: ">=sql-server-2017||>=sql-server-linux-2017"
 
 [!INCLUDE [SQL Server - Linux](../includes/applies-to-version/sql-linux.md)]
 
-In this tutorial, configure SQL Server snapshot replication on Linux with two instances of SQL Server using Transact-SQL. The publisher and distributor will be the same instance, and the subscriber will be on a separate instance.
+In this tutorial, configure SQL Server snapshot replication on Linux with two instances of SQL Server using Transact-SQL (T-SQL). The publisher and distributor will be the same instance, and the subscriber will be on a separate instance.
 
 > [!div class="checklist"]
 > * Enable SQL Server replication agents on Linux
@@ -111,7 +111,7 @@ To complete this tutorial, you will need:
    GO
    ```
 
-1. Configure publisher. Run the following TSQL commands on the publisher.
+1. Configure publisher. Run the following T-SQL commands on the publisher.
 
    ```sql
    DECLARE @publisher AS sysname
@@ -136,7 +136,7 @@ To complete this tutorial, you will need:
    GO
    ```
 
-1. Configure publication job. Run the following TSQL commands on the publisher.
+1. Configure publication job. Run the following T-SQL commands on the publisher.
 
    ```sql
    DECLARE @replicationdb AS sysname
@@ -176,7 +176,7 @@ To complete this tutorial, you will need:
    ```
 
 1. Create articles from the sales table
-   Run the following TSQL commands on the publisher.
+   Run the following T-SQL commands on the publisher.
 
    ```sql
    use [Sales]
@@ -196,7 +196,7 @@ To complete this tutorial, you will need:
    @vertical_partition = N'false'
    ```
 
-1. Configure Subscription. Run the following TSQL commands on the publisher.
+1. Configure Subscription. Run the following T-SQL commands on the publisher.
 
    ```sql
    DECLARE @subscriber AS sysname
@@ -263,15 +263,15 @@ To complete this tutorial, you will need:
    GO
    ```
 
-1. Connect subscriber and query replicated data.	
+1. Connect subscriber and query replicated data.    
 
    On the subscriber, check that the replication is working by running the following query:
 
    ```sql
    SELECT * from [Sales].[dbo].[CUSTOMER]
    ```
 
-In this tutorial, you configured SQL Server snapshot replication on Linux with two instances of SQL Server using Transact-SQL.
+In this tutorial, you configured SQL Server snapshot replication on Linux with two instances of SQL Server using T-SQL.
 
 > [!div class="checklist"]
 > * Enable SQL Server replication agents on Linux

docs/relational-databases/backup-restore/backup-encryption.md

@@ -97,7 +97,7 @@ The account that does backup operations on an encrypted database requires specif
 1. [Using Maintenance Plan Wizard](../../relational-databases/maintenance-plans/use-the-maintenance-plan-wizard.md#SSMSProcedure) When you select a backup task, on the **Options** tab of the **Define Backup ()Task** page, you can select **Backup Encryption**, and specify the encryption algorithm and the certificate or key to use for the encryption.  
 
 ### Using Transact-SQL  
- Following is a sample TSQL statement to encrypt the backup file:  
+ Following is a sample Transact-SQL statement to encrypt the backup file:  
 
 ```sql  
 BACKUP DATABASE [MYTestDB]  

docs/relational-databases/backup-restore/sql-server-backup-to-url-s3-compatible-object-storage-best-practices-and-troubleshooting.md

@@ -69,7 +69,7 @@ TO URL =  's3://<your-endpoint>/existingBucket/sqlbackups/AdventureWorks2022.bak
 
 ### Create a server-level credential prior to running backup/restore
 
-Before running backup/restore TSQL queries to S3-compatible storage, you must create a server level credential. This credential needs to contain the Access key and Secret Key set up by customers on their S3-compatible object storage server prior to issuing backup/restore queries.
+Before running backup/restore Transact-SQL queries to S3-compatible storage, you must create a server level credential. This credential needs to contain the Access key and Secret Key set up by customers on their S3-compatible object storage server prior to issuing backup/restore queries.
 
 An example of a credential that needs to be created for URL: `s3://<your-endpoint>/myS3Bucket/sqlbackups/AdventureWorks2022.bak` would be the following:
 
@@ -100,7 +100,7 @@ If there are multiple credentials matching search, such as more specific `s3://1
 
 Currently, the BACKUP TSQL option FILE_SNAPSHOT is not supported for S3-compatible object storage. This is an Azure Blob Storage-specific option.
 
-If the user runs the following TSQL for example:
+If the user runs the following Transact-SQL for example:
 
 ```sql
 BACKUP DATABASE AdventureWorks2022

docs/relational-databases/backup-restore/sql-server-backup-to-url.md

@@ -109,7 +109,7 @@ The following are security considerations and requirements when backing up to or
     > [!IMPORTANT]  
     >  Although the maximum backup size supported by a single block blob is 200 GB, it's possible for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to write in smaller block sizes, which can lead [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to reach the 50,000 block limit before the entire backup is transferred. Stripe backups (even if they're smaller than 200 GB) to avoid the block limit, especially when if you use differential or uncompressed backups.
 
-- You can issue backup or restore statements by using TSQL, SMO, PowerShell cmdlets, SQL Server Management Studio Backup or Restore wizard.
+- You can issue backup or restore statements by using Transact-SQL, SMO, PowerShell cmdlets, SQL Server Management Studio Backup or Restore wizard.
 
 - Backup to Azure Storage account using Azure Active Directory, User Managed or System Managed Identities is not supported by SQL Server.
 

docs/relational-databases/blob/filetable-compatibility-with-other-sql-server-features.md

@@ -37,7 +37,7 @@ helpviewer_keywords:
  Windows applications do not understand database transactions, so Windows write operations do not provide the ACID properties of a database transaction. Therefore transactional rollbacks and recovery are not possible with Windows update operations.  
 
  **Transact-SQL applications**  
- For TSQL applications working on the FILESTREAM (file_stream) column in a FileTable, the isolation semantics are the same as with FILESTREAM datatype in a regular user table.  
+ For Transact-SQL applications working on the FILESTREAM (file_stream) column in a FileTable, the isolation semantics are the same as with FILESTREAM datatype in a regular user table.  
 
 ##  <a name="OtherQueryNot"></a> Query Notifications and FileTables  
  The query cannot contain reference to the FILESTREAM column in the FileTable, in the WHERE clause or any other part of the query.  

docs/relational-databases/event-classes/tsql-event-category.md

@@ -15,7 +15,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 ---
 # TSQL Event Category
 [!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdb-asdbmi.md)]
-  The **TSQL** event category contains general TSQL events.  
+  The **TSQL** event category contains general Transact-SQL events.  
 
 ## In This Section  
 

docs/relational-databases/extended-events/use-the-ssms-xe-profiler.md

@@ -21,7 +21,7 @@ monikerRange: ">=sql-server-2016||>=sql-server-linux-2017"
 The XEvent Profiler is a SQL Server Management Studio (SSMS) feature that displays a live viewer window of Extended Events. This overview describes the reasons for using this profiler, key features, and instructions to get started viewing Extended Events.
 
 ## Why would I use the XEvent Profiler?
-Unlike SQL Profiler, XEvent profiler is directly integrated into SSMS and is built on top of the scalable Extended Events technology in the SQL engine. This feature enables quick access to a live streaming view of diagnostics events on the SQL Server. This view can be customized and those customizations can be shared with other SSMS users as a .viewsettings file. The session created by XE Profiler is less intrusive to the running SQL Server than a similar SQL trace would be when using SQL Profiler. This session can be customized by the user as well, using the existing XE session properties UI or by TSQL.
+Unlike SQL Profiler, XEvent profiler is directly integrated into SSMS and is built on top of the scalable Extended Events technology in the SQL engine. This feature enables quick access to a live streaming view of diagnostics events on the SQL Server. This view can be customized and those customizations can be shared with other SSMS users as a .viewsettings file. The session created by XE Profiler is less intrusive to the running SQL Server than a similar SQL trace would be when using SQL Profiler. This session can be customized by the user as well, using the existing XE session properties UI or by Transact-SQL.
 
 ## Prerequisites
 This feature is only available on SQL Server Management Studio (SSMS) v17.3 or later. Make sure you are using the latest version. You can find the latest version [here.](../../ssms/download-sql-server-management-studio-ssms.md)

docs/relational-databases/native-client-odbc-extensions-bulk-copy-functions/bcp-setbulkmode.md

@@ -247,7 +247,7 @@ BOOL BCPSetBulkMode(TCHAR * pszServer, TCHAR * pszQureryOut, char BCPType, TCHAR
                ODBCCleanUp();  
                return false;  
             }  
-            // set queryout TSQL statement  
+            // set queryout T-SQL statement  
             rc = bcp_control(g_hDbc, BCPHINTS , pszQureryOut);  
             if (SUCCEED != rc) {  
                printf("bcp_control(..BCP_OPTION_HINTS..) failed\n");  

docs/relational-databases/security/auditing/sql-server-audit-records.md

@@ -41,7 +41,7 @@ helpviewer_keywords:
 |**server_instance_name**|Name of the server instance where the audit occurred. Uses the standard machine\instance format.|**nvarchar(120)**|Yes|  
 |**database_name**|The database context in which the action occurred.|**sysname**|No|  
 |**schema_name**|The schema context in which the action occurred.|**sysname**|No|  
-|**object_name**|The name of the entity on which the audit occurred. This name can be:<br /><br /> server objects<br /><br /> databases<br /><br /> database objects<br /><br /> schema objects<br /><br /> TSQL statement (if any)|**sysname**|No|  
+|**object_name**|The name of the entity on which the audit occurred. This name can be:<br /><br /> server objects<br /><br /> databases<br /><br /> database objects<br /><br /> schema objects<br /><br /> Transact-SQL statement (if any)|**sysname**|No|  
 |**statement**|TSQL statement (if any)|**nvarchar(4000)**|No|  
 |**additional_information**|Any additional information about the event, stored as XML.|**nvarchar(4000)**|No|  
 

docs/relational-databases/stored-procedures/return-data-from-a-stored-procedure.md

@@ -192,7 +192,7 @@ EXECUTE @result = my_proc;
 GO
 ```  
 
-Return codes are commonly used in control-of-flow blocks within procedures to set the return code value for each possible error situation. You can use the `@@ERROR` function after a [!INCLUDE[tsql](../../includes/tsql-md.md)] statement to detect whether an error occurred during the execution of the statement. Before the introduction of `TRY`/`CATCH`/`THROW` error handling in TSQL return codes were sometimes required to determine the success or failure of stored procedures. Stored procedures should always indicate failure with an error (generated with `THROW`/`RAISERROR` if necessary), and not rely on a return code to indicate the failure. Also you should avoid using the return code to return application data.
+Return codes are commonly used in control-of-flow blocks within procedures to set the return code value for each possible error situation. You can use the `@@ERROR` function after a [!INCLUDE[tsql](../../includes/tsql-md.md)] statement to detect whether an error occurred during the execution of the statement. Before the introduction of `TRY`/`CATCH`/`THROW` error handling in Transact-SQL return codes were sometimes required to determine the success or failure of stored procedures. Stored procedures should always indicate failure with an error (generated with `THROW`/`RAISERROR` if necessary), and not rely on a return code to indicate the failure. Also you should avoid using the return code to return application data.
 
 ### Examples of return codes
 

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-nodes-exec-text-query-plan-transact-sql.md

@@ -1,6 +1,6 @@
 ---
 title: "sys.dm_pdw_nodes_exec_text_query_plan (Transact-SQL)"
-description: Dynamic management view that returns the Showplan in text format for a TSQL batch or for a specific statement within the batch.
+description: Dynamic management view that returns the Showplan in text format for a Transact-SQL batch or for a specific statement within the batch.
 author: jacinda-eng
 ms.author: jacindaeng
 ms.reviewer: wiassaf