Skip to content

Commit 4d3c721

Browse files
authored
Merge pull request #119290 from hyoshioka0128/patch-774
Typo "a Azure SQL Managed Instance"→"an Azure~"
2 parents 0fd219c + dc35632 commit 4d3c721

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/dms/howto-sql-server-to-azure-sql-managed-instance-powershell-offline.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ To complete these steps, you need:
4141
* To enable the TCP/IP protocol, which is disabled by default with SQL Server Express installation. Enable the TCP/IP protocol by following the article [Enable or Disable a Server Network Protocol](/sql/database-engine/configure-windows/enable-or-disable-a-server-network-protocol#SSMSProcedure).
4242
* To configure your [Windows Firewall for database engine access](/sql/database-engine/configure-windows/configure-a-windows-firewall-for-database-engine-access).
4343
* An Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
44-
* A SQL Managed Instance. You can create a SQL Managed Instance by following the detail in the article [Create a ASQL Managed Instance](/azure/azure-sql/managed-instance/instance-create-quickstart).
44+
* A SQL Managed Instance. You can create a SQL Managed Instance by following the detail in the article [Create an Azure SQL Managed Instance](/azure/azure-sql/managed-instance/instance-create-quickstart).
4545
* To download and install [Data Migration Assistant](https://www.microsoft.com/download/details.aspx?id=53595) v3.3 or later.
4646
* A Microsoft Azure Virtual Network created using the Azure Resource Manager deployment model, which provides the Azure Database Migration Service with site-to-site connectivity to your on-premises source servers by using either [ExpressRoute](../expressroute/expressroute-introduction.md) or [VPN](../vpn-gateway/vpn-gateway-about-vpngateways.md).
4747
* A completed assessment of your on-premises database and schema migration using Data Migration Assistant, as described in the article [Performing a SQL Server migration assessment](/sql/dma/dma-assesssqlonprem).
@@ -113,7 +113,7 @@ $sourceConnInfo = New-AzDmsConnInfo -ServerType SQL `
113113
-TrustServerCertificate:$true
114114
```
115115

116-
The next example shows creation of Connection Info for a Azure SQL Managed Instance named ‘targetmanagedinstance’:
116+
The next example shows creation of Connection Info for an Azure SQL Managed Instance named ‘targetmanagedinstance’:
117117

118118
```powershell
119119
$targetResourceId = (Get-AzSqlInstance -Name "targetmanagedinstance").Id
@@ -180,7 +180,7 @@ $backupFileShare = New-AzDmsFileShare -Path $backupFileSharePath -Credential $ba
180180

181181
The next step is to select the source and target databases by using the `New-AzDmsSelectedDB` cmdlet.
182182

183-
The following example is for migrating a single database from SQL Server to a Azure SQL Managed Instance:
183+
The following example is for migrating a single database from SQL Server to an Azure SQL Managed Instance:
184184

185185
```powershell
186186
$selectedDbs = @()
@@ -190,7 +190,7 @@ $selectedDbs += New-AzDmsSelectedDB -MigrateSqlServerSqlDbMi `
190190
-BackupFileShare $backupFileShare `
191191
```
192192

193-
If an entire SQL Server instance needs a lift-and-shift into a Azure SQL Managed Instance, then a loop to take all databases from the source is provided below. In the following example, for $Server, $SourceUserName, and $SourcePassword, provide your source SQL Server details.
193+
If an entire SQL Server instance needs a lift-and-shift into an Azure SQL Managed Instance, then a loop to take all databases from the source is provided below. In the following example, for $Server, $SourceUserName, and $SourcePassword, provide your source SQL Server details.
194194

195195
```powershell
196196
$Query = "(select name as Database_Name from master.sys.databases where Database_id>4)";

0 commit comments

Comments
 (0)