Skip to content

Commit affb566

Browse files
sabottasabotta
committed
completed copy edit
1 parent d64cc72 commit affb566

9 files changed

Lines changed: 110 additions & 106 deletions

‎docs/dma/dma-assesssqlonprem.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Assess your SQL Server Migration (Data Migration Assistant) | Microsoft Docs"
2+
title: "Assess your SQL Server migration (Data Migration Assistant) | Microsoft Docs"
33
ms.custom:
4-
ms.date: "08/24/2017"
4+
ms.date: "08/31/2017"
55
ms.prod: "sql-non-specified"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -19,8 +19,8 @@ ms.author: "carlasab"
1919
manager: "craigg"
2020
---
2121

22-
# Assess your SQL Server Migration
23-
The following step-by-step instructions will help you to perform your first assessment for migrating to either on-premises SQL Server or SQL Server running on Azure VM or Azure SQL Server database by using DMA.
22+
# Assess your SQL Server migration
23+
The following step-by-step instructions will help you to perform your first assessment for migrating to either on-premises SQL Server or SQL Server running on Azure VM, or to Azure SQL Server database, by using Data Migration Assistant.
2424

2525
# Create new assessment
2626

@@ -68,7 +68,7 @@ SQL Database**.
6868

6969
1. Click on **Add Sources** to open the connection fly-out.
7070

71-
2. Enter SQL server instance name, choose the Authentication type, set
71+
2. Enter the SQL server instance name, choose the Authentication type, set
7272
the correct connection properties, and then click **Connect**.
7373

7474
3. Select the databases to assess, and then click **Add**.
@@ -99,19 +99,19 @@ Compatibility issues can be reviewed by analyzing the impacted object and its de
9999

100100
![View assessment results](../dma/media/ReviewResults.png)
101101

102-
Similarly, you can review features’ recommendation across **Performance**, **Storage** and **Security** areas.
102+
Similarly, you can review feature recommendation across **Performance**, **Storage** and **Security** areas.
103103

104104
Feature recommendations cover a variety of features such as In-Memory OLTP and Columnstore, Stretch Database, Always Encrypted (AE), Dynamic Data Masking (DDM), and Transparent Data Encryption (TDE).
105105

106106
![View feature recommendations](../dma/media/FeatureRecommendations.png)
107107

108-
For "Azure SQL Database," the assessments provides migration blocking issues and feature parity issues.  Review the results for both categories by selecting the specific options.
108+
For Azure SQL Database, the assessments provide migration blocking issues and feature parity issues.  Review the results for both categories by selecting the specific options.
109109

110-
- The **SQL Server feature parity** category provides, currently in use at the source SQL Server. It then provides a comprehensive set of recommendations, alternative approaches available in Azure, and mitigating steps so that customers can plan this effort into their migration projects.
110+
- The **SQL Server feature parity** category provides a comprehensive set of recommendations, alternative approaches available in Azure, and mitigating steps so that you can plan this effort into your migration projects.
111111

112112
![View information for SQL Server feature parity](../dma/media/SQLFeatureParity.png)
113113

114-
- The **Compatibility issues** category provides partially or unsupported features that are the compatibility issues that block migrating on-premises SQL Server database(s)s to Azure SQL Database(s). It then provides recommendations to help customers remediate those issues.
114+
- The **Compatibility issues** category provides partially or unsupported features that are the compatibility issues that block migrating on-premises SQL Server database(s) to Azure SQL Database(s. It then provides recommendations to help you address those issues.
115115

116116
![View compatibility issues](../dma/media/CompatibilityIssues.png)
117117

‎docs/dma/dma-bestpractices.md‎

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Best Practices for Data Migration Assistant (SQL Server) | Microsoft Docs"
2+
title: "Best practices for Data Migration Assistant (SQL Server) | Microsoft Docs"
33
ms.custom:
4-
ms.date: "08/24/2017"
4+
ms.date: "08/31/2017"
55
ms.prod: "sql-non-specified"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -20,23 +20,27 @@ manager: "craigg"
2020
---
2121

2222

23-
# Best practices for Running Data Migration Assistant:
23+
# Best practices for running Data Migration Assistant
24+
This article provides the following best practice information for installation, assessments, and migration.
2425

26+
## Installation
2527

26-
**General**
28+
Do not install and run Data Migration Assistance directly on the SQL Server host machine.
2729

28-
Do not install and run Data Migration Assistance (DMA) directly on the SQL Server host machine.
29-
30-
**Assessment**
30+
## Assessment
3131

3232
- Run assessments on production databases during non-peak times.
3333

34-
- Perform the “Compatibility issues” and “New feature recommendations” assessments separately to reduce the assessment duration.
34+
- Perform the **Compatibility issues** and **New feature recommendations** assessments separately to reduce the assessment duration.
3535

36-
**Migration**
36+
## Migration
3737

3838
Migrate a server during non-peak times.
3939

40-
When migrating a database, provide a single share location accessible by source server and target server, and avoid copy operation if possible. Based on the size of the backup file, copy operation will introduce delay. It also increases the chances of failing migration due to an extra step. If a single location is provided, then DMA will bypass copy operation. However, please make sure that the correct permissions are given to the shared folder to avoid migration failures. The correct permissions are specified in the tool. If SQL Server instance runs under Network Service credentials, then give the machine account of the instance the correct permissions on the shared folder.
40+
When migrating a database, provide a single share location accessible by source server and target server,and avoid a copy operation if possible. Based on the size of the backup file, a copy operation will introduce delay. The operation also increases the chances of failing migration due to an extra step. When a single location is provided, Data Migration Assistant will bypass the copy operation.
41+
42+
Also, make sure that the correct permissions are given to the shared folder to avoid migration failures. The correct permissions are specified in the tool. If SQL Server instance runs under Network Service credentials, give the correct permissions on the shared folder to the machine account for the SQL Server instance .
43+
44+
Enable encrypt connection when connecting to the source and target servers. Using SSL encryption increases the security of data transmitted across the networks between Data Migration Assistant and the SQL Server instance. This is beneficial especially when migrating SQL logins. If SSL encryption is not used and the network is compromised by an attacker, the SQL logins being migrated could get intercepted and/or modified, on-the-fly by the attacker.
4145

42-
Enable "encrypt connection" when connecting to Source and Target server. Using SSL encryption increases the security of data transmitted across the networks between DMA and the SQL Server instance. This is beneficial especially when migrating SQL Logins. If SSL encryption is not used and the network is compromised by an attacker, then the SQL Logins being migrated could get intercepted and/or modified, on-the-fly by the attacker. However, if all access involves a secure intranet configuration, encryption might not be required. Enabling encryption does slow performance due to extra overhead to encrypt and decrypt packets. For more information please refer to [Encrypting Connections to SQL Server](https://go.microsoft.com/fwlink/?linkid=832513).
46+
However, if all access involves a secure intranet configuration, encryption might not be required. Enabling encryption does slow performance due to extra overhead to encrypt and decrypt packets. For more information please refer to [Encrypting Connections to SQL Server](https://go.microsoft.com/fwlink/?linkid=832513).

‎docs/dma/dma-commandline.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Run from Command Line (SQL Server Data Migration Assistant) | Microsoft Docs"
2+
title: "Run from command line (SQL Server Data Migration Assistant) | Microsoft Docs"
33
ms.custom:
4-
ms.date: "08/24/2017"
4+
ms.date: "08/31/2017"
55
ms.prod: "sql-non-specified"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -19,14 +19,14 @@ ms.author: "carlasab"
1919
manager: "craigg"
2020
---
2121

22-
# Run Data Migration Assistant from Command Line
23-
With DMA v2.1 and above when you install DMA, it will also install dmacmd.exe in *%ProgramFiles%\\Microsoft Data Migration Assistant\\. Use dmacmd.exe to assess your databases in an unattended mode. This is especially useful when assessing several databases or huge databases. Output the result to JSON or CSV file.
22+
# Run Data Migration Assistant from command line
23+
With version 2.1 and above, when you install Data Migration Assistant, it will also install dmacmd.exe in *%ProgramFiles%\\Microsoft Data Migration Assistant\\. Use dmacmd.exe to assess your databases in an unattended mode, and output the result to JSON or CSV file. This is especially useful when assessing several databases or huge databases.
2424

2525
> [!NOTE]
2626
> Dmacmd.exe supports running assessments only. Migrations are not supported at this time.
2727
2828

29-
## Command line arguments
29+
## Command-line arguments
3030

3131
```
3232
DmaCmd.exe /AssessmentName="string"
@@ -45,7 +45,7 @@ DmaCmd.exe /AssessmentName="string"
4545
|`/AssessmentDatabases` | Space delimited list of connection strings. Database name (Initial Catalog) is case sensitive. | Y
4646
|`/AssessmentTargetPlatform` | Target platform for the assessment, supported values: SqlServer2012, SqlServer2014, SqlServer2016 and AzureSqlDatabaseV12. Default is SqlServer2016 | N
4747
|`/AssessmentEvaluateFeatureParity` | Run feature parity rules | N
48-
|`/AssessmentEvaluateCompatibilityIssues` | Run compatibility rules. | Y <br> (Either AssessmentEvaluateCompatibilityIssues or AssessmentEvaluateRecommendations is required.)
48+
|`/AssessmentEvaluateCompatibilityIssues` | Run compatibility rules | Y <br> (Either AssessmentEvaluateCompatibilityIssues or AssessmentEvaluateRecommendations is required.)
4949
|`/AssessmentEvaluateRecommendations` | Run feature recommendations | Y <br> (Either AssessmentEvaluateCompatibilityIssues or AssessmentEvaluateRecommendationsis required)
5050
|`/AssessmentOverwriteResult` | Overwrite the result file | N
5151
|`/AssessmentResultJson` | Full path to the JSON result file | Y <br> (Either AssessmentResultJson or AssessmentResultCsv is required)
@@ -127,6 +127,6 @@ Catalog=DatabaseName3;Integrated Security=true"***
127127

128128

129129

130-
## See Also
130+
## See also
131131

132132
[Data Migration Assistant Download](https://www.microsoft.com/download/details.aspx?id=53595)

‎docs/dma/dma-configurationsettings.md‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Configuration Settings (SQL Server Data Migration Assistant) | Microsoft Docs"
2+
title: "Configuration settings (SQL Server Data Migration Assistant) | Microsoft Docs"
33
ms.custom:
4-
ms.date: "08/24/2017"
4+
ms.date: "08/31/2017"
55
ms.prod: "sql-non-specified"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -19,9 +19,9 @@ ms.author: "carlasab"
1919
manager: "craigg"
2020
---
2121

22-
# Configuration Settings for Data Migration Assistant
22+
# Configuration settings for Data Migration Assistant
2323

24-
You can fine-tune certain behavior of Data Migration Assistant using configuration values in the dma.exe.config file. Here are few key configuration values.
24+
You can fine-tune certain behavior of Data Migration Assistant using configuration values in the dma.exe.config file. This article describes key configuration values.
2525

2626
You can find the dma.exe.config file for the Data Migration Assistant desktop application and the command line utility, in the following folders on your machine.
2727

@@ -33,11 +33,11 @@ You can find the dma.exe.config file for the Data Migration Assistant desktop ap
3333

3434
%ProgramFiles%\\Microsoft Data Migration Assistant\\dmacmd.exe.config
3535

36-
Be sure to save a copy of the original config file before making any modification. After making changes, restart Data Migration Assistant for the new configuration values to take effect.
36+
Be sure to save a copy of the original config file before making any modifications. After making changes, restart Data Migration Assistant for the new configuration values to take effect.
3737

3838
## Number of databases to assess in parallel
3939

40-
DMA assesses multiple databases in parallel. During assessment DMA extracts data-tier application (dacpac) to understand the database schema. This operation can time-out if several databases on the same server are assessed in parallel.
40+
Data Migration Assistant assesses multiple databases in parallel. During assessment Data Migration Assistant extracts data-tier application (dacpac) to understand the database schema. This operation can time-out if several databases on the same server are assessed in parallel.
4141

4242
Starting with Data Migration Assistant v2.0, you can controll this by setting the parallelDatabases configuration value. Default value is 8.
4343

@@ -58,7 +58,7 @@ Starting with Data Migration Assistant v2.0, you can controll this by setting th
5858

5959
## Number of databases to migrate in parallel
6060

61-
Data Migration Assistant migrates multiple databases in parallel, before migrating logins. During migration, DMA will take a backup of the source database, optionally copy the backup, and then restore it on the target server. You may encounter timeout failures when several databases are selected for migration.
61+
Data Migration Assistant migrates multiple databases in parallel, before migrating logins. During migration, Data Migration Assistant will take a backup of the source database, optionally copy the backup, and then restore it on the target server. You may encounter timeout failures when several databases are selected for migration.
6262

6363
Starting with Data Migration Assistant v2.0, if you experience this problem you can reduce the parallelDatabases configuration value. You can increase the value to reduce the overall migration time.
6464

@@ -92,7 +92,7 @@ During assessment, Data Migration Assistant extracts data-tier application (dacp
9292

9393
- maxDataReaderDegreeOfParallelism
9494

95-
Number of Sql connection pool connections to use. (Default=8)
95+
Number of SQL connection pool connections to use. (Default=8)
9696

9797
```
9898
<advisorGroup>
@@ -108,12 +108,12 @@ maxDataReaderDegreeOfParallelism="8"/>
108108
```
109109

110110

111-
## Stretch Database: recommendation threshold
111+
## Stretch Database: Recommendation threshold
112112

113113
With [SQL Server Stretch
114-
Database](https://docs.microsoft.com/sql/sql-server/stretch-database/stretch-database), you can dynamically stretch warm and cold transactional data from Microsoft SQL Server 2016 to Azure. Stretch Database targets transactional databases with large amounts of cold data. The Stretch Database recommendation under Storage feature recommendation first identifies tables that it thinks will benefit from stretch, and then it identifies changes that need to be made to enable the table for stretch.
114+
Database](https://docs.microsoft.com/sql/sql-server/stretch-database/stretch-database), you can dynamically stretch warm and cold transactional data from Microsoft SQL Server 2016 to Azure. Stretch Database targets transactional databases with large amounts of cold data. The Stretch Database recommendation, under Storage feature recommendation, first identifies tables that it thinks will benefit from this feature, and then it identifies changes that need to be made to enable the table for this feature.
115115

116-
Starting with Data Migration Assistant v2.0, you can control this threshold for a table to qualify for stretch could using the recommendedNumberOfRows configuration value. Default value is 100,000 rows. If you want to analyze the stretch capabilities for even smaller tables, then lower the value accordingly.
116+
Starting with Data Migration Assistant v2.0, you can control this threshold for a table to qualify for the Stretch Database feature using the recommendedNumberOfRows configuration value. Default value is 100,000 rows. If you want to analyze the stretch capabilities for even smaller tables, then lower the value accordingly.
117117

118118
```
119119
<advisorGroup>
@@ -132,7 +132,7 @@ Starting with Data Migration Assistant v2.0, you can control this threshold for
132132

133133
You can control the [SQL connection
134134
time-out](https://msdn.microsoft.com/library/system.data.sqlclient.sqlconnection.connectiontimeout(v=vs.110).aspx)
135-
for source and target instances while running assessment or migration, by setting the connection timeout value to a specified number of seconds. The default value is 15 seconds.
135+
for source and target instances while running an assessment or migration, by setting the connection timeout value to a specified number of seconds. The default value is 15 seconds.
136136

137137
```
138138
<appSettings>
@@ -143,6 +143,6 @@ for source and target instances while running assessment or migration, by settin
143143
```
144144

145145

146-
## See Also
146+
## See also
147147

148148
[Data Migration Assistant Download](https://www.microsoft.com/download/details.aspx?id=53595)

0 commit comments

Comments
 (0)