Split up sqlcmd article (#34455)

Author: rwestMSFT

docs/toc.yml

@@ -8465,6 +8465,12 @@ items:
     items:
     - name: sqlcmd overview
       href: tools/sqlcmd/sqlcmd-utility.md
+    - name: Check installed version
+      href: tools/sqlcmd/sqlcmd-installed-version.md
+    - name: Download and install
+      href: tools/sqlcmd/sqlcmd-download-install.md
+    - name: sqlcmd edit and variable commands
+      href: tools/sqlcmd/sqlcmd-commands.md
     - name: Authenticate sqlcmd with Microsoft Entra ID
       href: tools/sqlcmd/sqlcmd-authentication.md
     - name: Start the utility

docs/tools/sqlcmd/edit-sqlcmd-scripts-query-editor.md

@@ -4,7 +4,7 @@ description: You use SQLCMD scripts when you have to process Windows System comm
 author: dlevy-msft
 ms.author: dlevy
 ms.reviewer: maghan, randolphwest
-ms.date: 08/15/2023
+ms.date: 07/02/2025
 ms.service: sql
 ms.subservice: tools-other
 ms.topic: how-to
@@ -77,17 +77,17 @@ To turn on SQLCMD scripting for an active Database Engine Query Editor window, u
    - (4 row(s) affected)
 
 > [!IMPORTANT]  
-> When executed from the command line, the **sqlcmd** utility permits full interaction with the operating system. When you use the Query Editor in **SQLCMD Mode**, you must be careful not to execute interactive statements. The Query Editor cannot respond to operating system prompts.
+> When executed from the command line, the **sqlcmd** utility permits full interaction with the operating system. When you use the Query Editor in **SQLCMD Mode**, you must be careful not to execute interactive statements. The Query Editor can't respond to operating system prompts.
 
-For more information about how to run SQLCMD, see [**sqlcmd** utility](sqlcmd-utility.md), or take the SQLCMD tutorial.
+For more information about how to run SQLCMD, see [sqlcmd utility](sqlcmd-utility.md), or take the SQLCMD tutorial.
 
 ## Enable SQLCMD scripting by default
 
 To turn on SQLCMD scripting by default, on the **Tools** menu, select **Options**, expand **Query Execution**, and **SQL Server**, select the **General** page and then check the **By default open new queries in SQLCMD Mode** box.
 
 ## Write and edit SQLCMD scripts
 
-After enabling scripting mode, you may write SQLCMD commands and Transact-SQL statements. The following rules apply:
+After enabling scripting mode, you can write SQLCMD commands and Transact-SQL statements. The following rules apply:
 
 - SQLCMD commands must be the first statement on a line.
 
@@ -103,12 +103,12 @@ After enabling scripting mode, you may write SQLCMD commands and Transact-SQL st
 
 - To make a clear distinction between SQLCMD commands and Transact-SQL, all SQLCMD commands need to be prefixed with a colon (`:`).
 
-- The `GO` command may be used without preface or preceded by `!!:`
+- The `GO` command can be used without preface or preceded by `!!:`
 
 - The Database Engine Query Editor supports environment variables and variables that are defined as part of a SQLCMD script, but doesn't support built-in SQLCMD or **osql** variables. SQLCMD processing by SQL Server Management Studio is case sensitive for variables. For example, PRINT '$(COMPUTERNAME)' produces the correct result, but PRINT '$(ComputerName)' returns an error.
 
 > [!CAUTION]  
-> SQL Server Management Studio uses [!INCLUDE [msCoName](../../includes/msconame-md.md)] [!INCLUDE [dnprdnshort](../../includes/dnprdnshort-md.md)] SqlClient for execution in regular and SQLCMD mode. When run from the command line, SQLCMD uses the OLE DB provider. Because different default options may apply, it is possible to get different behavior while executing the same query in SQL Server Management Studio SQLCMD Mode and in the SQLCMD utility.
+> SQL Server Management Studio uses [!INCLUDE [msCoName](../../includes/msconame-md.md)] [!INCLUDE [dnprdnshort](../../includes/dnprdnshort-md.md)] SqlClient for execution in regular and SQLCMD mode. When run from the command line, SQLCMD uses the OLE DB provider. Because different default options could apply, you can get different behavior while executing the same query in SQL Server Management Studio SQLCMD mode and in the **sqlcmd** utility.
 
 ## Supported SQLCMD syntax
 
@@ -131,13 +131,13 @@ The Database Engine Query Editor supports the following SQLCMD script keywords:
 SQLCMD commands not listed above aren't supported in Query Editor. When a script containing SQLCMD keywords aren't supported is executed, the Query Editor sends an "Ignoring command *\<ignored command*>" message to the destination for each unsupported keyword. The script executes successfully, but the unsupported commands are ignored.
 
 > [!CAUTION]  
-> Because you are not starting SQLCMD from the command line, there are some limitations when running Query Editor in SQLCMD Mode. You cannot pass in command-line parameters such as variables, and, because the Query Editor cannot respond to operating system prompts, you must be careful not to execute interactive statements.
+> Because you don't start SQLCMD from the command line, there are some limitations when running Query Editor in SQLCMD mode. You can't pass in command-line parameters such as variables, and, because the Query Editor can't respond to operating system prompts, you must be careful not to execute interactive statements.
 
 ## Color coding in SQLCMD scripts
 
 With SQLCMD scripting enabled, scripts are color coded. The color coding for Transact-SQL keywords remain the same. SQLCMD commands are presented with a shaded background.
 
-## Example
+## Examples
 
 The following example uses a SQLCMD statement to create an output file called testoutput.txt, executes two Transact-SQL SELECT statements along with one operating system command (to print the current directory). The resultant file contains the message output from the `DIR` statement and the results output from the Transact-SQL statements.
 
@@ -150,6 +150,6 @@ SELECT @@SERVERNAME AS 'Server Name';
 GO
 ```
 
-## Next steps
+## Related content
 
 - [sqlcmd utility](sqlcmd-utility.md)

docs/tools/sqlcmd/includes/install-go.md

@@ -4,7 +4,7 @@ description: A quickstart that walks through using creating a new container and
 author: dlevy-msft
 ms.author: dlevy
 ms.reviewer: maghan, randolphwest
-ms.date: 12/06/2023
+ms.date: 07/02/2025
 ms.service: sql
 ms.subservice: tools-other
 ms.topic: quickstart
@@ -22,7 +22,7 @@ In this quickstart, you'll use a single command in **sqlcmd** to create a new co
 ## Prerequisites
 
 - A container runtime installed, such as [Docker](https://www.docker.com/) or [Podman](https://podman.io/)
-- Download and install [[!INCLUDE [azure-data-studio](../../includes/azure-data-studio-short.md)]](/azure-data-studio/download-azure-data-studio)
+- Download and install [Azure Data Studio](/azure-data-studio/download-azure-data-studio)
 - Install the latest **sqlcmd**
 
 ## Remarks
@@ -35,7 +35,7 @@ You can reverse the order to make **sqlcmd** (ODBC) the default again.
 
 ## Download and install sqlcmd (Go)
 
-[!INCLUDE [install-go](includes/install-go.md)]
+For more information, see [Download and install the sqlcmd utility](sqlcmd-download-install.md#download-and-install-sqlcmd-go).
 
 ## What problem will we solve?
 
@@ -58,35 +58,35 @@ Open [!INCLUDE [azure-data-studio](../../includes/azure-data-studio-short.md)] a
 1. Now that you have a local copy of your database, you can run queries. Here is a query you can use to analyze spending by customer:
 
    ```sql
-   SELECT       bg.BuyingGroupName AS CustomerName
-                ,COUNT(DISTINCT i.InvoiceID) AS InvoiceCount
-                ,COUNT(il.InvoiceLineID) AS InvoiceLineCount
-                ,SUM(il.LineProfit) AS Profit
-                ,SUM(il.ExtendedPrice) AS ExtendedPrice
-   FROM         Sales.Invoices i
-                INNER JOIN Sales.Customers c 
-                    ON i.CustomerID = c.CustomerID
-                INNER JOIN Sales.InvoiceLines il 
-                    ON i.InvoiceID = il.InvoiceID
-                INNER JOIN Sales.BuyingGroups bg 
-                    ON c.BuyingGroupID = bg.BuyingGroupID
-   GROUP BY     bg.BuyingGroupName
+   SELECT bg.BuyingGroupName AS CustomerName,
+          COUNT(DISTINCT i.InvoiceID) AS InvoiceCount,
+          COUNT(il.InvoiceLineID) AS InvoiceLineCount,
+          SUM(il.LineProfit) AS Profit,
+          SUM(il.ExtendedPrice) AS ExtendedPrice
+   FROM Sales.Invoices AS i
+        INNER JOIN Sales.Customers AS c
+            ON i.CustomerID = c.CustomerID
+        INNER JOIN Sales.InvoiceLines AS il
+            ON i.InvoiceID = il.InvoiceID
+        INNER JOIN Sales.BuyingGroups AS bg
+            ON c.BuyingGroupID = bg.BuyingGroupID
+   GROUP BY bg.BuyingGroupName
    UNION
-   SELECT       c.CustomerName
-                ,COUNT(DISTINCT i.InvoiceID) AS InvoiceCount
-                ,COUNT(il.InvoiceLineID) AS InvoiceLineCount
-                ,SUM(il.LineProfit) AS Profit
-                ,SUM(il.ExtendedPrice) AS ExtendedPrice
-   FROM         Sales.Invoices i
-                INNER JOIN Sales.Customers c
-                    ON i.CustomerID = c.CustomerID
-                INNER JOIN Sales.InvoiceLines il
-                    ON i.InvoiceID = il.InvoiceID
-                LEFT JOIN Sales.BuyingGroups bg
-                    ON c.BuyingGroupID = bg.BuyingGroupID
-   WHERE        bg.BuyingGroupID IS NULL
-   GROUP BY     c.CustomerName
-   ORDER BY     Profit DESC
+   SELECT c.CustomerName,
+          COUNT(DISTINCT i.InvoiceID) AS InvoiceCount,
+          COUNT(il.InvoiceLineID) AS InvoiceLineCount,
+          SUM(il.LineProfit) AS Profit,
+          SUM(il.ExtendedPrice) AS ExtendedPrice
+   FROM Sales.Invoices AS i
+        INNER JOIN Sales.Customers AS c
+            ON i.CustomerID = c.CustomerID
+        INNER JOIN Sales.InvoiceLines AS il
+            ON i.InvoiceID = il.InvoiceID
+        LEFT OUTER JOIN Sales.BuyingGroups AS bg
+            ON c.BuyingGroupID = bg.BuyingGroupID
+   WHERE bg.BuyingGroupID IS NULL
+   GROUP BY c.CustomerName
+   ORDER BY Profit DESC;
    ```
 
 ## How did we solve the problem?