Merge pull request #22183 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

azure-sql/database/database-copy.md

@@ -61,7 +61,7 @@ New-AzSqlDatabaseCopy -ResourceGroupName "<resourceGroup>" -ServerName $sourcese
     -CopyResourceGroupName "myResourceGroup" -CopyServerName $targetserver -CopyDatabaseName "CopyOfMySampleDatabase"
 ```
 
-The database copy is an asynchronous operation but the target database is created immediately after the request is accepted. If you need to cancel the copy operation while still in progress, drop the the target database using the [Remove-AzSqlDatabase](/powershell/module/az.sql/new-azsqldatabase) cmdlet.
+The database copy is an asynchronous operation but the target database is created immediately after the request is accepted. If you need to cancel the copy operation while still in progress, drop the the target database using the [Remove-AzSqlDatabase](/powershell/module/az.sql/remove-azsqldatabase) cmdlet.
 
 For a complete sample PowerShell script, see [Copy a database to a new server](scripts/copy-database-to-new-server-powershell.md).
 

docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md

@@ -20,7 +20,7 @@ This quickstart shows how to use Azure Data Studio to connect to the Azure Cosmo
 
 To complete this quickstart, you need Azure Data Studio and an Azure Cosmos DB API account.
 
-- [Install Azure Data Studio](./download-azure-data-studio.md).
+- [Install Azure Data Studio](https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main).
 - [Install the Azure Cosmos DB API for MongoDB extension for Azure Data Studio](./extensions/azure-cosmos-db-mongodb-extension.md).
 - [Create an Azure Cosmos DB API for MongoDB account](/azure/cosmos-db/mongodb/mongodb-introduction).
 

docs/connect/odbc/linux-mac/install-microsoft-odbc-driver-sql-server-macos.md

@@ -22,6 +22,7 @@ This article provides commands for installing the ODBC driver from the bash shel
 
 > [!Note]
 > The Microsoft ODBC driver for SQL Server on macOS is only supported on the x64 architecture through version 17.7. Apple M1 (ARM64) support was added starting with version 17.8. The architecture will be detected and the correct package will be automatically installed by the Homebrew formula. If your command prompt is running in x64 emulation mode on the M1, the x64 package will be installed. If you're not running in emulation mode in your command prompt, the ARM64 package will be installed.
+> Additionally, the Homebrew default directory changed with the M1, to `/opt/homebrew`. The paths below use the x64 Homebrew paths, which default to `/usr/local`, so your file paths will vary accordingly.
 
 ## Microsoft ODBC 18
 

docs/relational-databases/system-dynamic-management-views/sys-dm-database-backups-azure-sql-database.md

@@ -56,3 +56,43 @@ SELECT *
 FROM sys.dm_database_backups     
 ORDER BY backup_finish_date DESC;  
 ```  
+You can get a friendlier resultset by joining to `sys.databases` and using a `CASE` statement. Run this query in the `master` database to get backup history for all databases in the Azure SQL Database server.
+ 
+```sql
+SELECT db.name
+    , backup_start_date
+    , backup_finish_date
+    , CASE backup_type
+        WHEN 'D' THEN 'Full'
+        WHEN 'I' THEN 'Differential'
+        WHEN 'L' THEN 'Transaction Log'
+    END AS BackupType
+    , CASE in_retention
+        WHEN 1 THEN 'In Retention'
+        WHEN 0 THEN 'Out of Retention'
+        END AS is_Bakcup_Available
+FROM sys.dm_database_backups AS ddb
+INNER JOIN sys.databases AS db
+    ON ddb.physical_database_name = db.physical_database_name
+ORDER BY backup_start_date DESC;
+```
+
+Run the below query in the user database context to get backup history for a single database.
+
+```sql
+SELECT backup_start_date
+    , backup_finish_date
+    , CASE backup_type
+        WHEN 'D' THEN 'Full'
+        WHEN 'I' THEN 'Differential'
+        WHEN 'L' THEN 'Transaction Log'
+        END AS BackupType
+    , CASE in_retention
+        WHEN 1 THEN 'In Retention'
+    WHEN 0 THEN 'Out of Retention'
+    END AS is_Bakcup_Available
+FROM sys.dm_database_backups AS ddb
+INNER JOIN sys.databases AS db
+    ON ddb.physical_database_name = db.physical_database_name
+ORDER BY backup_start_date DESC;
+```

docs/sql-server/azure-arc/connect.md

@@ -50,7 +50,7 @@ az provider register --namespace 'Microsoft.AzureArcData'
 
 ## Initiate the connection from Azure
 
-If the machine with SQL Server is already connected to Azure Arc, you can register the SQL Server instances on that machine by installing the SQL Server extension (*WindowsAgent.SqlServer*).  Once installed, the SQL Server extension will recognize all the installed SQL Server instances and register them with Azure Arc. The extension will run continuously to detect changes of the SQL Server configuration. For example, if a new SQL Server instance is installed on the machine, if will be automatically registered with Azure. See [virtual machine extension management](/azure/azure-arc/servers/manage-vm-extensions) for instructions how to install and uninstall extensions using  the Azure portal, Azure PowerShell or Azure CLI.
+If the machine with SQL Server is already connected to Azure Arc, you can register the SQL Server instances on that machine by installing the SQL Server extension (*WindowsAgent.SqlServer*).  Once installed, the SQL Server extension will recognize all the installed SQL Server instances and register them with Azure Arc. The extension will run continuously to detect changes of the SQL Server configuration. For example, if a new SQL Server instance is installed on the machine, if will be automatically registered with Azure. See [virtual machine extension management](/azure/azure-arc/servers/manage-vm-extensions) for instructions on how to install and uninstall extensions using the Azure portal, Azure PowerShell or Azure CLI.
 
 > [!IMPORTANT]
 >1. The Managed System Identity for the corresponding **Server - Azure Arc** must have the *Azure Connected SQL Server Onboarding* role at resource group level.

docs/sql-server/azure-arc/overview.md

@@ -73,7 +73,7 @@ Review [networking configuration, transport layer security, and resource provide
 
 The resource provider `Microsoft.AzureArcData` is required to connect the SQL Server instances to Azure Arc. To register the resource provider, follow the instructions in the [Prerequisites](connect.md#prerequisites) section.
 
-If you connected an instance of SQL Server ot Azure Arc prior to December 2020, you need to follow the [prerequisite steps](connect.md#prerequisites) to migrate the existing **SQL Server - Azure Arc** resources to the new namespace.
+If you connected an instance of SQL Server to Azure Arc prior to December 2020, you need to follow the [prerequisite steps](connect.md#prerequisites) to migrate the existing **SQL Server - Azure Arc** resources to the new namespace.
 
 ## Supported Azure regions
 

docs/t-sql/functions/string-split-transact-sql.md

@@ -97,7 +97,6 @@ In a practice run, the preceding SELECT returned following result table:
 |dolor|  
 |sit|  
 |amet.|  
-|   |
 
 The following example enables the `ordinal` column by passing 1 for the optional third argument:  
 
@@ -114,7 +113,6 @@ This statement then returns the following result table:
 |dolor|3|  
 |sit|4|  
 |amet.|5|  
-|   ||
 
 ## Examples  
 

docs/t-sql/queries/select-over-clause-transact-sql.md

@@ -620,7 +620,7 @@ ORDER BY SalesOrderNumber,ProductKey;
  The following example shows using the OVER clause with an aggregate function in a calculated value. Notice that the aggregates are calculated by `SalesOrderNumber` and the percentage of the total sales order is calculated for each line of each `SalesOrderNumber`.  
 
 ```sql  
--- Uses AdventureWorks  
+-- Uses AdventureWorksDW2019
 
 SELECT SalesOrderNumber AS OrderNumber, ProductKey AS Product,   
        OrderQuantity AS Qty,