debuglevel
diff --git a/‎azure-sql/database/authentication-aad-configure.md‎
Lines changed: 34 additions & 22 deletions b/‎azure-sql/database/authentication-aad-configure.md‎
Lines changed: 34 additions & 22 deletions
diff --git a/‎azure-sql/database/connect-query-go.md‎
Lines changed: 13 additions & 12 deletions b/‎azure-sql/database/connect-query-go.md‎
Lines changed: 13 additions & 12 deletions
diff --git a/‎azure-sql/database/recovery-using-backups.md‎
Lines changed: 4 additions & 4 deletions b/‎azure-sql/database/recovery-using-backups.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎azure-sql/database/security-best-practice.md‎
Lines changed: 1 addition & 1 deletion b/‎azure-sql/database/security-best-practice.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/database-engine/configure-windows/connect-to-sql-server-when-system-administrators-are-locked-out.md‎
Lines changed: 11 additions & 11 deletions b/‎docs/database-engine/configure-windows/connect-to-sql-server-when-system-administrators-are-locked-out.md‎
Lines changed: 11 additions & 11 deletions
@@ -5,7 +5,7 @@ description: Use Go to create a program that connects to a database in Azure SQL
 author: dlevy-msft
 ms.author: dlevy
 ms.reviewer: wiassaf, mathoma
-ms.date: 07/26/2023
+ms.date: 08/22/2023
 ms.service: sql-database
 ms.subservice: connect
 ms.topic: quickstart
@@ -59,21 +59,14 @@ Get the connection information you need to connect to the database. You'll need
 > [!NOTE]
 > For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
 
-## Create Golang project and dependencies
+## Create a new folder for the Golang project and dependencies
 
 1. From the terminal, create a new project folder called **SqlServerSample**. 
 
    ```bash
    mkdir SqlServerSample
    ```
 
-2. Navigate to **SqlServerSample** and install the SQL Server driver for Go.
-
-   ```bash
-   cd SqlServerSample
-   go get github.com/microsoft/go-mssqldb
-   ```
-
 ## Create sample data
 
 1. In a text editor, create a file called **CreateTestData.sql** in the **SqlServerSample** folder. In the file, paste this T-SQL code, which creates a schema, table, and inserts a few rows.
@@ -306,15 +299,23 @@ Get the connection information you need to connect to the database. You'll need
    }
    ```
 
-## Run the code
+## Get Golang project dependencies and run the code
+
+1. At the command prompt, navigate to **SqlServerSample** and install the SQL Server driver for Go by running the following commands.
+
+   ```bash
+   cd SqlServerSample
+   go mod init SqlServerSample
+   go mod tidy
+   ```
 
-1. At the command prompt, run the following command.
+2. At the command prompt, run the following command.
 
    ```bash
    go run sample.go
    ```
 
-2. Verify the output.
+3. Verify the output.
 
    ```text
    Connected!
 
@@ -5,7 +5,7 @@ description: Learn about point-in-time restore, which enables you to roll back a
 author: SudhirRaparla
 ms.author: nvraparl
 ms.reviewer: wiassaf, mathoma, danil
-ms.date: 07/20/2022
+ms.date: 08/21/2023
 ms.service: sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -96,7 +96,7 @@ You generally restore a database to an earlier point for recovery purposes. You
 
   If you plan to retrieve data from the restored database to recover from a user or application error, you need to write and run a data recovery script that extracts data from the restored database and applies to the original database. Although the restore operation might take a long time to complete, the restoring database is visible in the database list throughout the restore process. 
 
-  If you delete the database during the restore, the restore operation will be canceled. You won't be charged for the database that did not complete the restore.
+  If you delete the database during the restore, the restore operation will be canceled. You won't be charged for the database that didn't complete the restore.
 
 ### [Azure portal](#tab/azure-portal)
 
@@ -138,7 +138,7 @@ To restore a database by using the REST API:
 
 ## Long-term backup restore
 
-To perform a restore operation on a long-term backup, you can use the Azure portal, the Azure CLI, Azure PowerShell, or the REST API. For more information, see [Restore a long-term backup](long-term-backup-retention-configure.md#view-backups-and-restore-from-a-backup). Long-term retention is not applicable to Hyperscale databases. 
+To perform a restore operation on a long-term backup, you can use the Azure portal, the Azure CLI, Azure PowerShell, or the REST API. For more information, see [Restore a long-term backup](long-term-backup-retention-configure.md#view-backups-and-restore-from-a-backup). Long-term retention isn't applicable to Hyperscale databases. 
 
 ### [Azure portal](#tab/azure-portal)
 
@@ -283,7 +283,7 @@ For more information on using geo-restore, see [Recovery using Geo-restore](reco
 > [!NOTE]
 > For detailed information about recover from an outage, see [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md) and the [Azure SQL Database high availability and disaster recovery checklist](high-availability-disaster-recovery-checklist.md). 
 
-Geo-restore is the most basic disaster-recovery solution available in SQL Database. It relies on automatically created geo-replicated backups with a recovery point objective (RPO) of up to 1 hour and an estimated recovery time objective (RTO) of up to 12 hours. It doesn't guarantee that the target region will have the capacity to restore your databases after a regional outage, because a sharp increase of demand is likely. If your application uses relatively small databases and is not critical to the business, geo-restore is an appropriate disaster-recovery solution. 
+Geo-restore is the most basic disaster-recovery solution available in SQL Database. It relies on automatically created geo-replicated backups with a recovery point objective (RPO) of up to 1 hour and an estimated recovery time objective (RTO) of up to 12 hours. It doesn't guarantee that the target region will have the capacity to restore your databases after a regional outage, because a sharp increase of demand is likely. If your application uses relatively small databases and isn't critical to the business, geo-restore is an appropriate disaster-recovery solution. 
 
 For business-critical applications that require large databases and must ensure business continuity, use [auto-failover groups](auto-failover-group-sql-db.md). That feature offers a much lower RPO and RTO, and the capacity is always guaranteed. 
 
 
@@ -159,7 +159,7 @@ Password-based authentication methods are a weaker form of authentication. Crede
 **Best practices**
 
 - Use single sign-on authentication using Windows credentials. Federate the on-premises AD domain with Azure AD and use integrated Windows authentication (for domain-joined machines with Azure AD).
-  - See the article, [SSMS support for Azure AD Integrated authentication](authentication-aad-configure.md#active-directory-integrated-authentication).
+  - See the article, [SSMS support for Azure AD Integrated authentication](authentication-aad-configure.md#azure-active-directory---integrated).
 
 ### Minimize the use of password-based authentication for applications
 
 
@@ -3,7 +3,7 @@ title: "Connect to SQL Server when system administrators are locked out"
 description: Learn how to regain access to SQL Server as a system administrator if you've been mistakenly locked out.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 07/14/2022
+ms.date: 08/21/2023
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
@@ -25,15 +25,15 @@ This article describes how you can regain access to the [!INCLUDE[ssDEnoversion]
 
 - The logins that are members of the sysadmin fixed server role are for individuals who have left the company or who aren't available.
 
-- The sa account is disabled or no one knows the password.
+- The `sa` account is disabled or no one knows the password.
 
 ## Resolution
 
 In order to resolve your access issue, we recommend that you start the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode. This mode prevents other connections from occurring while you try to regain access. From here, you can connect to your instance of SQL Server and add your login to the **sysadmin** server role. Detailed steps for this solution are provided in the [step-by-step-instructions](#step-by-step-instructions) section.
 
 You can start an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode with either the `-m` or `-f` options from the command line. Any member of the computer's local Administrators group can then connect to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] as a member of the **sysadmin** fixed server role.
 
-When you start the instance in single-user mode, first stop the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent service. Otherwise, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent might connect first, taking the only available connection to the server and blocking you from logging in.
+When you start the instance in single-user mode, stop the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent service. Otherwise, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent might connect first, taking the only available connection to the server and blocking you from logging in.
 
 It's also possible for an unknown client application to take the only available connection before you're able to sign in. In order to prevent this from happening, you can use the `-m` option followed by an application name to limit connections to a single connection from the specified application. For example, starting [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] with `-mSQLCMD` limits connections to a single connection that identifies itself as the **sqlcmd** client program. To connect through the Query Editor in [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)], use `-m"Microsoft SQL Server Management Studio - Query"`.
 
@@ -55,10 +55,10 @@ For step-by-step instructions about how to start [!INCLUDE[ssNoVersion](../../in
 
 ### Use PowerShell
 
-#### Option 1: Run the steps directly in an executable notebook via Azure Data Studio
+#### Option 1: Run the steps directly in an executable notebook using Azure Data Studio
 
 > [!NOTE]  
-> Before attempting to open this notebook, check that Azure Data Studio is installed on your local machine. To install, go to [Learn how to install Azure Data Studio](../../azure-data-studio/download-azure-data-studio.md).
+> Before attempting to open this notebook, check that Azure Data Studio is installed on your local machine. To install Azure Data Studio, see [Learn how to install Azure Data Studio](../../azure-data-studio/download-azure-data-studio.md).
 
 > [!div class="nextstepaction"]
 > [Open Notebook in Azure Data Studio](azuredatastudio://microsoft.notebook/open?url=https://raw.githubusercontent.com/microsoft/mssql-support/master/sample-scripts/DOCs-to-Notebooks/T-shooting-SQL-SystemAdmins-Locked-out.ipynb)
@@ -108,7 +108,7 @@ For step-by-step instructions about how to start [!INCLUDE[ssNoVersion](../../in
    > `Sqlcmd: Error: Microsoft ODBC Driver X for SQL Server : Login failed for user 'CONTOSO\BobD'. Reason: Server is in single user mode. Only one administrator can connect at this time..`
 
 1. **Mixed Mode (optional):** If your SQL Server is running in mixed authentication mode, you can also:
-    1. Grant the Sysadmin role membership to a SQL login. Execute code such as the following to create a new SQL Server authentication login that is a member of the sysadmin fixed server role. Replace "?j8:z$G=JE9" with a strong password of your choice.
+    1. Grant the **sysadmin** role membership to a SQL login. Execute code such as the following to create a new SQL Server authentication login that is a member of the **sysadmin** fixed server role. Replace `?j8:z$G=JE9` with a strong password of your choice.
 
        If you have a default instance, use the name of the server.
 
@@ -117,7 +117,7 @@ For step-by-step instructions about how to start [!INCLUDE[ssNoVersion](../../in
        sqlcmd.exe -E -S $sql_server_instance -Q "CREATE LOGIN TempLogin WITH PASSWORD = '$strong_password'; ALTER SERVER ROLE sysadmin ADD MEMBER TempLogin; "
        ```
 
-    1. Also, if your SQL Server is running in mixed authentication mode and you want to reset the password of an enabled **sa** account. Change the password of the sa account with the following syntax. Be sure to replace "j8:zG=J?E9" with a strong password of your choice:
+    1. Also, if your SQL Server is running in mixed authentication mode and you want to reset the password of an enabled **sa** account. Change the password of the sa account with the following syntax. Be sure to replace `j8:zG=J?E9` with a strong password of your choice:
 
        If you have a default instance, use the name of the server.
 
@@ -151,17 +151,17 @@ Perform these instructions while logged in to Windows as a member of the local a
 
 1. On the **Startup Parameters** tab, in the **Specify a startup parameter** box, type `-m` and then select **Add**. (That's a dash then lower case letter m.)
 
-   For some earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] there is no **Startup Parameters** tab. In that case, on the **Advanced** tab, double-click **Startup Parameters**. The parameters open up in a small window. Be careful not to change any of the existing parameters. At the very end, add a new parameter `;-m` and then select **OK**. (That's a semi-colon then a dash then lower case letter m.)
+   For some earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], there's no **Startup Parameters** tab. In that case, on the **Advanced** tab, double-click **Startup Parameters**. The parameters open up in a small window. Be careful not to change any of the existing parameters. At the very end, add a new parameter `;-m` and then select **OK**. (That's a semi-colon then a dash then lower case letter m.)
 
 1. Select **OK**, and after the message to restart, right-click your server name, and then select **Restart**.
 
 1. After [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] has restarted, your server will be in single-user mode. Make sure that [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent isn't running. If started, it will take your only connection.
 
-1. From the Windows Start menu, right-click the icon for [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)] and select **Run as administrator**. This will pass your administrator credentials to SSMS.
+1. From the Windows Start menu, right-click the icon for [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)] and select **Run as administrator**. This passes your administrator credentials to SSMS.
 
    For earlier versions of Windows, the **Run as administrator** option appears as a submenu.
 
-   In some configurations, SSMS will attempt to make several connections. Multiple connections will fail because [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is in single-user mode. Based on your scenario, perform one of the following actions.
+   In some configurations, SSMS attempts to make several connections. Multiple connections will fail because [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is in single-user mode. Based on your scenario, perform one of the following actions.
 
    1. Connect with Object Explorer using Windows Authentication, which includes your Administrator credentials. Expand **Security**, expand **Logins**, and double-click your own login. On the **Server Roles** page, select **sysadmin**, and then select **OK**.
 
@@ -199,7 +199,7 @@ Perform these instructions while logged in to Windows as a member of the local a
 
 1. On the **Startup Parameters** tab, in the **Existing parameters** box, select `-m` and then select **Remove**.
 
-   For some earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] there is no **Startup Parameters** tab. In that case, on the **Advanced** tab, double-click **Startup Parameters**. The parameters open up in a small window. Remove the `;-m` that you added earlier, and then select **OK**.
+   For some earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], there's no **Startup Parameters** tab. In that case, on the **Advanced** tab, double-click **Startup Parameters**. The parameters open up in a small window. Remove the `;-m` that you added earlier, and then select **OK**.
 
 1. Right-click your server name, and then select **Restart**. Make sure to start [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent again if you stopped it before starting [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode.