Fix 5 UUF items: JDBC DLL wording, ODBC version mapping, DataSource recommendation, PREDICT syntax differences, Node.js Windows auth (#36727)

VanMSFT · web-flow · commit 96a7447a4d3d · 2026-02-27T10:03:46.000-08:00
diff --git a/docs/connect/jdbc/building-the-connection-url.md b/docs/connect/jdbc/building-the-connection-url.md
@@ -4,7 +4,7 @@ description: Learn about formatting the connection string used by the Microsoft
 author: David-Engel
 ms.author: davidengel
 ms.reviewer: vanto
-ms.date: 09/12/2024
+ms.date: 02/26/2026
 ms.service: sql
 ms.subservice: connectivity
 ms.topic: how-to
@@ -23,12 +23,12 @@ Where:
 
 - **serverName** (Optional) - Is the address of the server to connect to. This address can be a DNS or IP address, or it can be `localhost` or `127.0.0.1` for the local computer. If not specified in the connection URL, the server name must be specified in the properties collection.
 
-- **instanceName** (Optional) - Is the instance to connect to on `serverName`. If not specified, a connection to the default instance is made.
+- **instanceName** (Optional) - Is the instance to connect to on `serverName`. If not specified, the driver connects to the default instance.
 
 - **portNumber** (Optional) - Is the port to connect to on `serverName`. The default is `1433`. If you're using the default port, you don't have to specify the port, nor the preceding `:` in the URL.
 
     > [!NOTE]  
-    > For optimal connection performance, you should set the `portNumber` when you connect to a named instance. This will avoid a round trip to the server to determine the port number. If both a `portNumber` and `instanceName` are used, the `portNumber` will take precedence and the `instanceName` will be ignored.
+    > For optimal connection performance, set the `portNumber` when you connect to a named instance. This avoids a round trip to the server to determine the port number. If you use both a `portNumber` and `instanceName`, the `portNumber` takes precedence and the `instanceName` is ignored.
 
 - **property** (Optional) - Is one or more option connection properties. For more information, see [Setting the connection properties](setting-the-connection-properties.md). Any property from the list can be specified. Properties can only be delimited by using the semicolon (`;`), and they can't be duplicated.
 
@@ -72,7 +72,7 @@ jdbc:sqlserver://;servername=server_name;encrypt=true;integratedSecurity=true;au
 
 ## Named and multiple SQL Server instances
 
-[!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] allows for the installation of multiple database instances per server. Each instance is identifiable by a specific name. To connect to a named instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], you can either specify the port number of the named instance (preferred). You can also specify the instance name as a JDBC URL property or a **datasource** property. If no instance name or port number property is specified, a connection to the default instance is created. See the following examples:
+[!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] allows for the installation of multiple database instances per server. Each instance has a specific name. To connect to a named instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], you can either specify the port number of the named instance (preferred). You can also specify the instance name as a JDBC URL property or a **datasource** property. If you don't specify an instance name or port number property, the driver creates a connection to the default instance. See the following examples:
 
 - To specify a port number, use the following format:
 
@@ -97,7 +97,10 @@ In version 8.4 and above, escaped values can contain special characters, includi
 
 ## <a name="Connectingintegrated"></a> Connecting with integrated authentication On Windows
 
-The JDBC driver supports the use of Type 2 integrated authentication on Windows operating systems by using the `integratedSecurity` connection string property. To use integrated authentication, copy the `mssql-jdbc_auth-<version>-<arch>.dll` file to a directory on the Windows system path on the computer where the JDBC driver is installed.
+The JDBC driver supports the use of Type 2 integrated authentication on Windows operating systems by using the `integratedSecurity` connection string property. To use integrated authentication, copy the `mssql-jdbc_auth-<version>-<arch>.dll` file to any directory that is included in the Windows system `PATH` environment variable.
+
+> [!NOTE]
+> The DLL doesn't need to be in the same directory as the JDBC driver JAR file. It only needs to be in a directory listed in the system `PATH`, for example `C:\Windows\System32` or a custom directory that you add to `PATH`.
 
 The `mssql-jdbc_auth-<version>-<arch>.dll` files are installed in the following location:
 
@@ -106,9 +109,9 @@ The `mssql-jdbc_auth-<version>-<arch>.dll` files are installed in the following
 For any operating system supported by the [!INCLUDE [jdbcNoVersion](../../includes/jdbcnoversion_md.md)], see [Using Kerberos integrated authentication to connect to SQL Server](using-kerberos-integrated-authentication-to-connect-to-sql-server.md) for a description of a feature added in [!INCLUDE [jdbc-40](../../includes/jdbc-40-md.md)] that allows an application to connect to a database using integrated authentication with Type 4 Kerberos.
 
 > [!NOTE]  
-> If you are running a 32-bit Java Virtual Machine (JVM), use the `mssql-jdbc_auth-<version>-<arch>.dll` file in the x86 folder, even if the operating system is the x64 version. If you are running a 64-bit JVM on a x64 processor, use the `mssql-jdbc_auth-<version>-<arch>.dll` file in the x64 folder.
+> If you're running a 32-bit Java Virtual Machine (JVM), use the `mssql-jdbc_auth-<version>-<arch>.dll` file in the x86 folder, even if the operating system is the x64 version. If you're running a 64-bit JVM on a x64 processor, use the `mssql-jdbc_auth-<version>-<arch>.dll` file in the x64 folder.
 
-Alternatively you can set the java.library.path system property to specify the directory of the `mssql-jdbc_auth-<version>-<arch>.dll`. For example, if the JDBC driver is installed in the default directory, you can specify the location of the DLL by using the following virtual machine (VM) argument when the Java application is started:
+Alternatively, you can set the java.library.path system property to specify the directory of the `mssql-jdbc_auth-<version>-<arch>.dll`. For example, if you installed the JDBC driver in the default directory, you can specify the location of the DLL by using the following virtual machine (VM) argument when the Java application starts:
 
 `-Djava.library.path=C:\Microsoft JDBC Driver 6.4 for SQL Server\sqljdbc_<version>\enu\auth\x86`
 
diff --git a/docs/connect/jdbc/using-the-jdbc-driver.md b/docs/connect/jdbc/using-the-jdbc-driver.md
@@ -3,7 +3,7 @@ title: Using the JDBC driver
 description: This section provides quick start instructions to make a simple connection to a SQL Server database using the Microsoft JDBC Driver for SQL Server.
 author: David-Engel
 ms.author: davidengel
-ms.date: 03/17/2025
+ms.date: 02/26/2026
 ms.service: sql
 ms.subservice: connectivity
 ms.topic: quickstart
@@ -462,7 +462,7 @@ The following snippet is an example of the CLASSPATH statement that's used for a
 Make sure that the CLASSPATH statement contains only one [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)], such as either sqljdbc.jar, sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar.  
   
 > [!NOTE]  
-> On Windows systems, directory names longer than the 8.3 filename convention or folder names with spaces may cause problems with classpaths. If you suspect these types of issues, you should temporarily move the sqljdbc.jar file, sqljdbc4.jar file, or the sqljdbc41.jar file into a simple directory name such as `C:\Temp`, change the classpath, and determine whether that addresses the problem.  
+> On Windows systems, directory names longer than the 8.3 filename convention or folder names with spaces may cause problems with classpaths. If you suspect these types of problems, temporarily move the sqljdbc.jar file, sqljdbc4.jar file, or the sqljdbc41.jar file into a simple directory name such as `C:\Temp`, change the classpath, and determine whether that addresses the problem.  
   
 ### Applications that are run directly at the command prompt
 
@@ -494,17 +494,23 @@ Connection con = DriverManager.getConnection(connectionUrl);
 ```
 
 > [!WARNING]  
-> The above connection string uses `encrypt=false`, which is not recommended for production use. For more information about encrypting your database connection with JDBC, see [Connecting with encryption](connecting-with-ssl-encryption.md).
+> The above connection string uses `encrypt=false`, which isn't recommended for production use. For more information about encrypting your database connection with JDBC, see [Connecting with encryption](connecting-with-ssl-encryption.md).
 
 Starting from JDBC API 4.0, the `DriverManager.getConnection()` method is enhanced to load JDBC drivers automatically. Therefore, applications don't need to call the `Class.forName` method to register or load the driver when using driver jar libraries.  
   
-When the getConnection method of the DriverManager class is called, an appropriate driver is located from the set of registered JDBC drivers. sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar file includes "META-INF/services/java.sql.Driver" file, which contains the **com.microsoft.sqlserver.jdbc.SQLServerDriver** as a registered driver. The existing applications, which currently load the drivers by using the Class.forName method, will continue to work without modification.  
+When you call the getConnection method of the DriverManager class, it locates an appropriate driver from the set of registered JDBC drivers. sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar file includes "META-INF/services/java.sql.Driver" file, which contains the **com.microsoft.sqlserver.jdbc.SQLServerDriver** as a registered driver. The existing applications, which currently load the drivers by using the Class.forName method, continue to work without modification.  
   
 > [!NOTE]  
-> sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar class library cannot be used with older versions of the Java Runtime Environment (JRE). See [System requirements for the JDBC driver](../../connect/jdbc/system-requirements-for-the-jdbc-driver.md) for the list of JRE versions supported by the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)].  
+> sqljdbc4.jar, sqljdbc41.jar, or sqljdbc42.jar class library can't be used with older versions of the Java Runtime Environment (JRE). See [System requirements for the JDBC driver](../../connect/jdbc/system-requirements-for-the-jdbc-driver.md) for the list of JRE versions supported by the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)].  
 
 For more information about how to connect with data sources and use a connection URL, see [Building the connection URL](../../connect/jdbc/building-the-connection-url.md) and [Setting the connection properties](../../connect/jdbc/setting-the-connection-properties.md).  
-  
-## See also  
 
-[Overview of the JDBC driver](../../connect/jdbc/overview-of-the-jdbc-driver.md)  
+> [!TIP]
+> The previous example uses `DriverManager` for simplicity. For production applications, consider using the `SQLServerDataSource` class instead, which provides connection pooling and additional configurability. For more information and examples, see [Connecting and retrieving data](connecting-and-retrieving-data.md) and [Data source sample](data-source-sample.md).
+
+## Related content
+
+- [Overview of the JDBC driver](../../connect/jdbc/overview-of-the-jdbc-driver.md)
+- [Building the connection URL](../../connect/jdbc/building-the-connection-url.md)
+- [Setting the connection properties](../../connect/jdbc/setting-the-connection-properties.md)
+- [Connecting and retrieving data](connecting-and-retrieving-data.md)
diff --git a/docs/connect/node-js/step-3-proof-of-concept-connecting-to-sql-using-node-js.md b/docs/connect/node-js/step-3-proof-of-concept-connecting-to-sql-using-node-js.md
@@ -3,7 +3,7 @@ title: "Step 3: Connecting to SQL using Node.js"
 description: "This example should be considered a proof of concept showing how to connect to SQL using Node.js and is simplified for clarity."
 author: David-Engel
 ms.author: davidengel
-ms.date: "07/23/2019"
+ms.date: "02/26/2026"
 ms.service: sql
 ms.subservice: connectivity
 ms.topic: install-set-up-deploy
@@ -12,11 +12,11 @@ ms.topic: install-set-up-deploy
 
 :::image type="icon" source="../../includes/media/download.svg" border="false"::: **[Download Node.js SQL driver](../sql-connection-libraries.md#anchor-20-drivers-relational-access)**
 
-This example should be considered a proof of concept only. The sample code is simplified for clarity, and does not necessarily represent best practices recommended by Microsoft. Other examples, which use the same crucial functions are available in the [GitHub sample repository](https://github.com/tediousjs/tedious/blob/master/examples/).
+This example should be considered a proof of concept only. The sample code is simplified for clarity, and doesn't necessarily represent best practices recommended by Microsoft. Other examples, which use the same crucial functions are available in the [GitHub sample repository](https://github.com/tediousjs/tedious/blob/master/examples/).
   
 ## Step 1: Connect  
   
-The **new Connection** function is used to connect to SQL Database.  
+Use the **new Connection** function to connect to SQL Database.  
   
 ```javascript  
     var Connection = require('tedious').Connection;  
@@ -30,7 +30,7 @@ The **new Connection** function is used to connect to SQL Database.
             }
         },
         options: {
-            // If you are on Microsoft Azure, you need encryption:
+            // If you're on Microsoft Azure, you need encryption:
             encrypt: true,
             database: 'your_database'  //update me
         }
@@ -48,7 +48,7 @@ The **new Connection** function is used to connect to SQL Database.
 ## Step 2:  Execute a query  
   
   
-All SQL statements are executed using the **new Request()** function. If the statement returns rows, such as a select statement, you can retrieve them using the **request.on()** function. If there are no rows, the request.on() function returns empty lists.  
+Execute all SQL statements using the **new Request** function. If the statement returns rows, such as a select statement, you can retrieve them using the **request.on** function. If there are no rows, the request.on function returns empty lists.  
   
   
 ```javascript  
@@ -63,7 +63,7 @@ All SQL statements are executed using the **new Request()** function. If the sta
             }
         },
         options: {
-            // If you are on Microsoft Azure, you need encryption:
+            // If you're on Microsoft Azure, you need encryption:
             encrypt: true,
             database: 'your_database'  //update me
         }
@@ -112,7 +112,7 @@ All SQL statements are executed using the **new Request()** function. If the sta
   
 ## Step 3: Insert a row  
   
-In this example you will see how to execute an [INSERT](../../t-sql/statements/insert-transact-sql.md) statement safely, passing parameters, which protect your application from [SQL injection](../../relational-databases/security/sql-injection.md) values.    
+In this example, you see how to execute an [INSERT](../../t-sql/statements/insert-transact-sql.md) statement safely, passing parameters, which protect your application from [SQL injection](../../relational-databases/security/sql-injection.md) values.    
   
   
 ```javascript  
@@ -127,7 +127,7 @@ In this example you will see how to execute an [INSERT](../../t-sql/statements/i
             }
         },
         options: {
-            // If you are on Microsoft Azure, you need encryption:
+            // If you're on Microsoft Azure, you need encryption:
             encrypt: true,
             database: 'your_database'  //update me
         }
@@ -170,3 +170,46 @@ In this example you will see how to execute an [INSERT](../../t-sql/statements/i
         connection.execSql(request);  
     }  
 ```  
+
+## Step 4: Connect with Windows authentication
+
+The tedious driver supports Windows authentication using NTLM. To connect with domain credentials instead of SQL Server authentication, change the `authentication` section in the connection configuration:
+
+```javascript
+var Connection = require('tedious').Connection;
+var config = {
+    server: '<server>',  //update me
+    authentication: {
+        type: 'ntlm',
+        options: {
+            domain: '<domain>',    //update me
+            userName: '<username>', //update me
+            password: '<password>'  //update me
+        }
+    },
+    options: {
+        encrypt: false,
+        database: '<database>',  //update me
+        port: 1433
+    }
+};
+var connection = new Connection(config);
+connection.on('connect', function(err) {
+    if (err) {
+        console.log('Connection failed', err);
+    } else {
+        console.log('Connected with Windows authentication');
+    }
+});
+
+connection.connect();
+```
+
+> [!NOTE]
+> NTLM authentication requires you to provide domain credentials in the configuration. For trusted connections that use the currently logged-in Windows user without specifying credentials, consider the [msnodesqlv8](https://www.npmjs.com/package/msnodesqlv8) package, which uses the native ODBC driver.
+
+## Related content
+
+- [Node.js driver for SQL Server](node-js-driver-for-sql-server.md)
+- [Step 1: Configure development environment for Node.js development](step-1-configure-development-environment-for-node-js-development.md)
+- [Step 2: Create a SQL database for Node.js development](step-2-create-a-sql-database-for-node-js-development.md)
diff --git a/docs/database-engine/configure-windows/open-the-odbc-data-source-administrator.md b/docs/database-engine/configure-windows/open-the-odbc-data-source-administrator.md
@@ -4,7 +4,7 @@ description: Find out how to open the ODBC Data Source Administrator on various
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: vanto
-ms.date: 08/26/2025
+ms.date: 02/26/2026
 ms.service: sql
 ms.subservice: configuration
 ms.topic: how-to
@@ -36,6 +36,23 @@ Your computer might contain a variety of ODBC drivers, from [!INCLUDE [msCoName]
 
   Information for the Microsoft [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] entry is displayed in the **Version** column.
 
+### Understand ODBC driver version numbers
+
+The **Version** column in the ODBC Data Source Administrator displays the internal file version number, which differs from the marketing version name used in product downloads and documentation.
+
+The following table maps common marketing version names to their corresponding internal file version patterns:
+
+| Marketing version | Internal file version pattern |
+|---|---|
+| ODBC Driver 18 for SQL Server | 2022.*x*.*x* |
+| ODBC Driver 17 for SQL Server | 2017.*x*.*x* |
+| ODBC Driver 13.1 for SQL Server | 2015.*x*.*x* |
+| ODBC Driver 13 for SQL Server | 2014.*x*.*x* |
+
+For example, if the **Version** column shows `2017.177.02.01`, the installed driver corresponds to **ODBC Driver 17 for SQL Server**.
+
+For detailed release history, see [Release notes for the Microsoft ODBC Driver for SQL Server on Windows](../../connect/odbc/windows/release-notes-odbc-sql-server-windows.md).
+
 ## Related content
 
 - [ODBC Data Source Administrator](../../odbc/admin/odbc-data-source-administrator.md)
diff --git a/docs/t-sql/queries/predict-transact-sql.md b/docs/t-sql/queries/predict-transact-sql.md
