initial updates

haywoodsloan · haywoodsloan · commit 769f21702140 · 2026-01-21T15:38:01.000-05:00
diff --git a/support/sql/releases/find-my-sql-version.md b/support/sql/releases/find-my-sql-version.md
@@ -1,34 +1,46 @@
 ---
-title: Determine the version and edition of SQL Server Database Engine
-description: This article describes the procedures to determine the version and edition of SQL Server Database Engine that is running.
-ms.date: 01/10/2025
+title: Find the Version and Edition of Your SQL Server Database Engine
+description: Learn how to find your the version and edition of your SQL Server Database Engine using methods like SSMS, error logs, T-SQL queries, and more.
+ms.date: 01/21/2025
 ms.topic: how-to
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
-ms.reviewer: v-six, jopilov
+ms.reviewer: jopilov, v-shaywood
 ---
 
 <!---Internal note: The screenshots in the article are being or were already updated. Please contact "gsprad" and "aartigoyle" for triage before making the further changes to the screenshots.
 --->
 
 # Determine which version and edition of SQL Server Database Engine is running
 
-This article describes the procedures to determine the version and edition of SQL Server Database Engine that is running.
-
 _Original product version:_ &nbsp; SQL Server  
 _Original KB number:_ &nbsp; 321185
 
-To determine the version of SQL Server, you can use any of the following methods.
+## Summary
+
+Knowing your SQL Server Database Engine version and edition is essential for troubleshooting, planning upgrades, and ensuring compatibility. This article explains several methods to determine this information, including SQL Server Management Studio (SSMS), error log files, T-SQL queries, and the SQL Server Installation Center.
 
 > [!NOTE]  
->  The version information follows the *major.minor.build.revision* pattern. The "revision" information is typically not used when checking the version of SQL Server.
+> The version information follows the `major.minor.build.revision` pattern. The "revision" information is typically not used when checking the version of SQL Server.
+
+## Choose your method to determine version and edition
 
-## Method 1: Connect to the server by using SQL Server Management Studio
+| Method                                                                         | Best for                   | Requirements                      |
+| ------------------------------------------------------------------------------ | -------------------------- | --------------------------------- |
+| [Object Explorer (SSMS)](#use-object-explorer-in-sql-server-management-studio) | Quick visual check         | SSMS installed, server connection |
+| [Errorlog file](#view-the-errorlog-file)                                       | No connection needed       | File system access                |
+| [SELECT @@VERSION](#run-the-query-select-version)                              | Scripting and automation   | Query access                      |
+| [SERVERPROPERTY](#use-the-serverproperty-function)                             | Individual property values | Query access                      |
+| [Discovery report](#use-the-installed-sql-server-features-discovery-report)    | All instances on system    | Local access only                 |
 
-Connect to the server by using Object Explorer in [SQL Server Management Studio (SSMS)](/sql/ssms/sql-server-management-studio-ssms). Once connected, the version information will be displayed in parentheses, along with the username used to connect to the specific instance of SQL Server. For more information on how to connect to SQL Server using Object Explorer, see [Connect to a SQL Server or Azure SQL Database](/sql/ssms/object/connect-to-an-instance-from-object-explorer).
+## Use Object Explorer in SQL Server Management Studio
 
-## Method 2: Look at the first few lines of the Errorlog file
+Connect to the server by using Object Explorer in [SQL Server Management Studio (SSMS)](/sql/ssms/sql-server-management-studio-ssms). Once connected, the version information will be displayed in parentheses, along with the username used to connect to the specific instance of SQL Server. 
 
-Look at the first few lines of the *Errorlog* file for that instance. By default, the error log is located at `Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG` in _ERRORLOG.n_ files. The entries may resemble the following one:
+For more information on how to connect to SQL Server using Object Explorer, see [Connect to a SQL Server or Azure SQL Database](/sql/ssms/object/connect-to-an-instance-from-object-explorer).
+
+## View the Errorlog file
+
+Look at the first few lines of the `Errorlog` file for that instance. By default, the error log is located at `Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG` in `ERRORLOG.n` files. The entries may resemble the following one:
 
 ```output
 2024-09-05 16:56:22.35 Server      Microsoft SQL Server 2022 (RTM-CU14) (KB5038325) - 16.0.4135.4 (X64)  
@@ -39,7 +51,7 @@ Developer Edition (64-bit) on Windows 11 Enterprise 10.0 <X64> (Build 22631: ) (
 
 This entry provides information about the product, such as version, product level, 64-bit versus 32-bit, the edition of SQL Server, and the OS version on which SQL Server is running.
 
-## Method 3: Look at the output after running the query "SELECT @@VERSION"
+## Run the query "SELECT @@VERSION"
 
 Connect to the instance of SQL Server, and then run the following query:
 
@@ -55,7 +67,7 @@ Microsoft SQL Server 2022 (RTM-CU14) (KB5038325) - 16.0.4135.4 (X64)   Jul 10 20
 
 From the output, you can determine the SQL Server product's version, service pack level, cumulative update level, or security update level (if applicable).
 
-## Method 4: Use the SERVERPROPERTY function 
+## Use the SERVERPROPERTY function
 
 Connect to the instance of SQL Server, and then run the following query in [SSMS](/sql/ssms/sql-server-management-studio-ssms):
 
@@ -71,9 +83,9 @@ The following results are returned:
 
 For example, the results resemble the following.
 
-|Product version|Product level|Edition|
-|---|---|---|
-| 16.0.4135.4|RTM| Developer Edition (64-bit) |
+| Product version | Product level | Edition                    |
+| --------------- | ------------- | -------------------------- |
+| 16.0.4135.4     | RTM           | Developer Edition (64-bit) |
 
 > [!NOTE]
 >
@@ -83,9 +95,11 @@ For example, the results resemble the following.
 >
 > - Starting with [SQL Server 2014 RTM Cumulative Update 10](https://support.microsoft.com/help/3094220) and [SQL Server 2014 Service Pack 1 Cumulative Update 3](https://support.microsoft.com/help/3094221), additional properties have been added to the `SERVERPROPERTY` statement. For a complete list, see [SERVERPROPERTY (Transact-SQL)](/sql/t-sql/functions/serverproperty-transact-sql).
 
-## Method 5: Use the "Installed SQL Server features discovery report"
+## Use the "Installed SQL Server features discovery report"
+
+You can find the **Installed SQL Server features discovery report** on the **Tools** page of the SQL Server Installation Center. This report provides information about all the instances of SQL Server that are installed on the system, including client tools such as SSMS. Note that this tool can be run locally only on the system where SQL Server is installed. It can't be used to obtain information about remote servers. 
 
-You can also use the **Installed SQL Server features discovery report**. You can find this report on the **Tools** page of the SQL Server Installation Center. This tool provides information about all the instances of SQL Server that are installed on the system, including client tools such as SSMS. Note that this tool can be run locally only on the system where SQL Server is installed. It can't be used to obtain information about remote servers. For more information, see [Validate a SQL Server Installation](/sql/database-engine/install-windows/validate-a-sql-server-installation).
+For more information, see [Validate a SQL Server Installation](/sql/database-engine/install-windows/validate-a-sql-server-installation).
 
 A snapshot of a sample report is as follows:
 
@@ -94,4 +108,4 @@ A snapshot of a sample report is as follows:
 ## See also
 
 - [Determine version information of SQL Server components and client tools](components-client-tools-versions.md)
-- [Latest updates and version history for SQL Server](download-and-install-latest-updates.md)
+- [Latest updates and version history for SQL Server](download-and-install-latest-updates.md)
