Merge pull request #9749 from haywoodsloan/7530-update-headings

AB#7530: Update headings in 4 SQL articles - AI Headings Optimization Experiment

Author: haywoodsloan

support/sql/azure-sql/sql-installation-fails-sector-size-error-azure-vm.md

@@ -53,7 +53,7 @@ To resolve this problem, reinstall SQL Server after forcing the Azure VM to use
 To successfully install SQL Server on your Azure VM, follow these steps:
 
 1. If you've already installed SQL Server, uninstall SQL Server. Otherwise, skip to the next step. 
-1. Add the [ForcedPhysicalSectorSizeInBytes](../database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolutions) registry key. 
+1. Add the [ForcedPhysicalSectorSizeInBytes](../database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolution-steps-for-disk-sector-size-errors-in-sql-server) registry key. 
 1. Verify the sector size is 4 KB by running the following command in an elevated command prompt:
 
    `fsutil fsinfo sectorinfo <volume pathname>`

support/sql/database-engine/connect/certificate-chain-not-trusted.md

@@ -18,7 +18,7 @@ If you recently upgraded your SQL Server Native Client 11.0 (Provider=SQLNCLI11)
 
 > [Microsoft OLE DB Driver 19 for SQL Server]: SSL Provider: The certificate chain was issued by an authority that is not trusted.
 
-### Cause
+### Cause of Certificate Chain Trust Error in SNAC applications
 
 These errors occur if both the following conditions are true:
 
@@ -28,7 +28,7 @@ These errors occur if both the following conditions are true:
 
 The error occurs because of a change in the default behavior of the client drivers. Older versions of client drivers are designed to assume that data encryption is **OFF** by default. The new drivers assume this setting to be **ON** by default. Because data encryption is set to **ON**, the driver tries to validate the server's certificate and fails.
 
-### Solutions
+### Solutions for Certificate Chain Trust Error in SNAC applications
 
 - **Solution 1:** Use Microsoft OLE DB Driver for SQL Server 18.x. You can download the driver from [Release notes for the Microsoft OLE DB Driver for SQL Server](/sql/connect/oledb/release-notes-for-oledb-driver-for-sql-server).
 
@@ -48,7 +48,7 @@ If you recently upgraded your SQL Server Native Client 11.0 (Driver={SQL Server
 
 > [Microsoft][ODBC Driver 18 for SQL Server]Client unable to establish connection
 
-### Cause
+### Cause of Certificate Chain Trust Error in SNAC applications
 
 These errors occur if both the following conditions are true:
 
@@ -58,7 +58,7 @@ These errors occur if both the following conditions are true:
 
 The error occurs because of a change in the default behavior of the client drivers. Older versions of client drivers are designed to assume that data encryption is **OFF** by default. The new drivers assume this setting to be **ON** by default. Because data encryption is set to **ON**, the driver tries to validate the server's certificate and fails.
 
-### Solutions
+### Solutions for Certificate Chain Trust Error in SNAC applications
 
 - **Solution 1:** Use the Microsoft ODBC Driver 17 for SQL Server. You can download the driver from [Download ODBC Driver for SQL Server](/sql/connect/odbc/download-odbc-driver-for-sql-server).
 

support/sql/database-engine/connect/network-related-or-instance-specific-error-occurred-while-establishing-connection.md

@@ -11,9 +11,9 @@ ms.reviewer: jopilov
 
 _Applies to:_   SQL Server
 
-When connecting to a SQL Server instance, you may encounter one or more of the following [error messages](#error-messages). This article provides some steps to help you troubleshoot these errors, which are provided in order of the issues from simple to complex.
+When connecting to a SQL Server instance, you may encounter one or more [error messages](#common-sql-server-connection-error-messages). This article explains how to [collect the necessary information](#gather-information-to-troubleshoot-sql-server-connection-errors) to diagnose these issues and outlines a structured troubleshooting approach to help you resolve these issues, starting with basic checks and moving on to more advanced techniques.
 
-## Error messages
+## Common SQL Server connection error messages
 
 The complete error messages vary depending on the client library that's used in the application and the server environment. You can check the following details to see if you're encountering one of the following error messages:
 
@@ -97,7 +97,7 @@ The complete message is:
 
 This message means that SQL Server isn't listening on the Shared Memory or Named Pipes protocol.
 
-## Gather information for troubleshooting the error
+## Gather information to troubleshoot SQL Server connection errors
 
 We recommend that you gather the information listed in this section using one of the following options before proceeding with the actual steps to troubleshoot the error.
 

support/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md

@@ -8,7 +8,7 @@ author: WilliamDAssafMSFT
 ms.author: wiassaf
 ---
 
-# Troubleshoot errors related to system disk sector size greater than 4 KB
+# Troubleshoot SQL Server errors related to system disk sector size greater than 4 KB
 
 This article provides solutions for troubleshooting errors during installation or starting an instance of SQL Server on Windows. This article is valid for all released versions of SQL Server.
 
@@ -76,7 +76,7 @@ You install any version of SQL Server on a Windows 10 device. Then, you upgrade
 2021-11-05 23:42:47.14 spid9s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\master.mdf. 
 ```
 
-## Scenario 5
+## Scenario 5: SQL Server application error from ntdll.dll
 
 You install any version of SQL Server on a Windows 10 device. Then, you upgrade the OS on the device to Windows 11. When you try to start SQL Server on a Windows 11 device, the service fails to start. In the SQL Server error log, you notice the following entries:
 
@@ -111,7 +111,7 @@ Source             : SQLLocalDB 11.0
 > [!Note]
 > You might encounter the failures mentioned in the previous scenarios for a SQL Server instance you installed manually or on a LocalDB instance installed by applications.
 
-## Cause
+## Cause of disk sector size errors in SQL Server
 
 During service startup, SQL Server begins the database recovery process to ensure database consistency. Part of this database recovery process involves consistency checks on the underlying filesystem before you try to open system and user database files.  
 
@@ -138,7 +138,7 @@ Additionally, be aware of the Windows support policy for file system and storage
 > [!NOTE]
 > There's no released version of SQL Server compatible with sector sizes greater than 4 KB. For more information, see the [Hard disk drive sector-size support boundaries in SQL Server](https://support.microsoft.com/topic/hard-disk-drive-sector-size-support-boundaries-in-sql-server-4d5b73fa-7dc4-1d8a-2735-556e6b60d046) article.
 
-## Resolutions
+## Resolution steps for disk sector size errors in SQL Server
 
 - Currently, the `ForcedPhysicalSectorSizeInBytes` registry key is required to successfully install SQL Server when using modern storage platforms, such as NVMe, that provide a sector size larger than 4 KB. This Windows operating system registry key forces the sector size to be emulated as 4 KB.
 

support/sql/database-engine/performance/performance-degradation-misaligned-io-sector-error.md

@@ -55,7 +55,7 @@ The following screenshot shows the output of the `fsutil fsinfo sectorinfo` comm
 
 ## Resolution 
 
-If you're experiencing performance degradation due to misaligned I/O operations and can't [modify your sector size](../database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolutions), you can use [Trace Flag 1800](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf1800) as a global startup parameter to force SQL Server to use a consistent 4-KB sector size for transaction log I/O operations.
+If you're experiencing performance degradation due to misaligned I/O operations and can't [modify your sector size](../database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolution-steps-for-disk-sector-size-errors-in-sql-server), you can use [Trace Flag 1800](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf1800) as a global startup parameter to force SQL Server to use a consistent 4-KB sector size for transaction log I/O operations.
 
 To enable Trace Flag 1800 as a startup parameter, follow these steps:
 

support/sql/database-engine/security/transfer-logins-passwords-between-instances.md

@@ -10,15 +10,11 @@ ms.topic: how-to
 
 # Transfer logins and passwords between instances of SQL Server
 
- This article describes how to transfer the logins and the passwords between different instances of SQL Server running on Windows.
+This article describes how to transfer the logins and passwords between different instances of Microsoft SQL Server running on Windows. The instances might be on the same server or different servers, and their versions might differ.
 
 _Original product version:_   SQL Server  
 _Original KB number:_   918992, 246133
 
-## Introduction
-
-This article describes how to transfer the logins and passwords between different instances of Microsoft SQL Server. The instances might be on the same server or different servers, and their versions might differ.
-
 ## Why transfer logins between SQL Server instances?
 
 In this article, server A and server B are servers.
@@ -31,7 +27,7 @@ This problem occurs because the logins from the SQL Server instance on server A
 
 Keep in mind that error 18456 occurs for many other reasons. For more information on these causes and their resolutions, see [MSSQLSERVER_18456](/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error).
 
-## Steps to transfer the logins
+## Steps to transfer logins between SQL Server instances
 
 To transfer the logins, use one of the following methods, as appropriate for your situation.
 
@@ -288,37 +284,37 @@ To generate scripts via SSMS on the source server and manually reset passwords f
      ```
 
 1. The output script that the `sp_help_revlogin` stored procedure generates is the login script. This login script creates the logins that have the original Security Identifier (SID) and the original password.
-1. Review and follow the information in the [Remarks](#remarks) section before you proceed with implementing steps on the destination server.
-1. Once you implement any applicable steps from the [Remarks](#remarks) section, connect to the destination server B using any client tool (like SSMS).
+1. Review and follow the information in the [Additional considerations when transferring SQL Server logins](#additional-considerations-when-transferring-sql-server-logins) section before you proceed with implementing steps on the destination server.
+1. Once you implement any applicable steps from the [Additional considerations when transferring SQL Server logins](#additional-considerations-when-transferring-sql-server-logins) section, connect to the destination server B using any client tool (like SSMS).
 1. Run the script generated as the output of `sp_helprevlogin` from server A.
 
-## Remarks
+## Additional considerations when transferring SQL Server logins
 
 Review the following information before you run the output script on the instance on server B:
 
-### Password hashing information
+### Understand password hashing in SQL Server login transfers
 
 - A password can be hashed in the following ways:
 
   - `VERSION_SHA1`: This hash is generated by using the SHA1 algorithm and is used in SQL Server 2000 through SQL Server 2008 R2.
   - `VERSION_SHA2`: This hash is generated by using the SHA2 512 algorithm and is used in SQL Server 2012 and later versions.
 - In the output script, the logins are created by using the encrypted password. This is because of the `HASHED` argument in the `CREATE LOGIN` statement. This argument specifies that the password that is entered after the `PASSWORD` argument is already hashed.
 
-### How to handle the change of domains
+### Handle domain changes during SQL Server login transfers
 
 Are your source and destination servers in different domains? Review the output script carefully. If server A and server B are in different domains, you have to change the output script. Then, you have to replace the original domain name by using the new domain name in the `CREATE LOGIN` statements. The integrated logins that are granted access in the new domain don't have the same SID as the logins in the original domain. Therefore, users are orphaned from these logins. For more information about how to resolve these orphaned users, see [Troubleshoot orphaned users (SQL Server)](/sql/sql-server/failover-clusters/troubleshoot-orphaned-users-sql-server) and [ALTER USER](/sql/t-sql/statements/alter-user-transact-sql).  
 
 If server A and server B are in the same domain, the same SID is used. Therefore, users are unlikely to be orphaned.
 
-### Permissions to view and select all logins
+### Required permissions to view and select SQL Server logins
 
 By default, only a member of the sysadmin fixed server role can run a `SELECT` statement from the `sys.server_principals` view. Unless a member of the sysadmin fixed server role grants the necessary permissions to the users, the users can't create or run the output script.
 
 ### Default database setting isn't scripted and transferred
 
 The steps in this article don't transfer the default database information for a particular login. This is because the default database might not always exist on server B. To define the default database for a login, use the `ALTER LOGIN` statement by passing in the login name and the default database as arguments.
 
-### How to deal with different sort orders between the source and destination servers
+### Manage sort order differences in SQL Server login transfers
 
 There might be differences in sort orders between the source and destination servers, or they might be the same. Here's how each scenario can be addressed:
 
@@ -330,7 +326,7 @@ There might be differences in sort orders between the source and destination ser
 
 - **Case-sensitive or case-insensitive on both servers**: The sort order of both server A and server B might be case-sensitive, or the sort order of both server A and server B might be case-insensitive. In these cases, the users don't experience a problem.
 
-### How to deal with logins already existing on the destination server
+### Resolve conflicts with existing SQL Server logins on destination server
 
 The script is designed to check if the login exists on the destination server and create a login only if it doesn't. However, if you receive the following error message when you run the output script on the instance on server B, you have to manually resolve it by following the steps in this section.