Skip to content

Commit a97dff6

Browse files
HJToland3HJToland3
committed
dma fix
1 parent a7360bc commit a97dff6

12 files changed

Lines changed: 74 additions & 64 deletions

‎docs/dma/dma-assesssqlonprem.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Perform a SQL Server migration assessment (Data Migration Assistant) | Microsoft Docs"
33
description: Learn how to use Data Migration Assistant to assess an on-premises SQL Server before migrating to another SQL Server or to Azure SQL Database
44
ms.custom: ""
5-
ms.date: "08/29/2018"
5+
ms.date: "10/20/2018"
66
ms.prod: sql
77
ms.prod_service: "dma"
88
ms.reviewer: ""
@@ -12,7 +12,7 @@ keywords: ""
1212
helpviewer_keywords:
1313
- "Data Migration Assistant, Assess"
1414
ms.assetid: ""
15-
author: HJToland3
15+
author: pochiraju
1616
ms.author: rajpo
1717
manager: craigg
1818
---
@@ -28,7 +28,7 @@ The following step-by-step instructions help you perform your first assessment f
2828

2929
2. Set the source and target server type.
3030

31-
If you are upgrading your on-premises SQL Server instance to a modern on-premises SQL Server instance or to SQL Server hosted on an Azure VM, set the source and target server type to **SQL Server**. If you are migrating to Azure SQL Database, instead set the target server type to **Azure SQL Database**.
31+
If you're upgrading your on-premises SQL Server instance to a modern on-premises SQL Server instance or to SQL Server hosted on an Azure VM, set the source and target server type to **SQL Server**. If you're migrating to Azure SQL Database, instead set the target server type to **Azure SQL Database**.
3232

3333
3. Click **Create**.
3434

@@ -40,15 +40,15 @@ The following step-by-step instructions help you perform your first assessment f
4040

4141
2. Select the report type.
4242

43-
When you are assessing your source SQL Server instance for migrating to on-premises SQL Server or to SQL Server hosted on Azure VM targets, you can choose one or both of the following assessment report types:
43+
When you're assessing your source SQL Server instance for migrating to on-premises SQL Server or to SQL Server hosted on Azure VM targets, you can choose one or both of the following assessment report types:
4444

4545
- **Compatibility Issues**
4646

4747
- **New features’ recommendation**
4848

4949
![Select an assessment report type for SQL Server target](../dma/media/AssessmentTypes.png)
5050

51-
When you are assessing your source SQL Server instance for migrating to Azure SQL Database, you can choose one or both of the following assessment report types:
51+
When you're assessing your source SQL Server instance for migrating to Azure SQL Database, you can choose one or both of the following assessment report types:
5252

5353
- **Check database compatibility**
5454

@@ -73,7 +73,7 @@ The following step-by-step instructions help you perform your first assessment f
7373

7474
## View results
7575

76-
The duration of the assessment depends on the number of databases added and the schema size of each database. Results are displayed for each database as soon as they are available.
76+
The duration of the assessment depends on the number of databases added and the schema size of each database. Results are displayed for each database as soon as they're available.
7777

7878
1. Select the database that has completed the assessment, and then switch between **Compatibility issues** and **Feature recommendations** by using the switcher.
7979

‎docs/dma/dma-bestpractices.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Best practices for Data Migration Assistant (SQL Server) | Microsoft Docs"
33
description: Learn best practices for migrating SQL Server databases with Data Migration Assistant
44
ms.custom: ""
5-
ms.date: "08/29/2018"
5+
ms.date: "10/20/2018"
66
ms.prod: sql
77
ms.prod_service: "dma"
88
ms.reviewer: ""
@@ -12,7 +12,7 @@ keywords: ""
1212
helpviewer_keywords:
1313
- "Data Migration Assistant, Best Practices"
1414
ms.assetid: ""
15-
author: HJToland3
15+
author: pochiraju
1616
ms.author: rajpo
1717
manager: craigg
1818
---
@@ -22,7 +22,7 @@ manager: craigg
2222
This article provides some best practice information for installation, assessment, and migration.
2323

2424
## Installation
25-
Do not install and run the Data Migration Assistant directly on the SQL Server host machine.
25+
Don't install and run the Data Migration Assistant directly on the SQL Server host machine.
2626

2727
## Assessment
2828
- Run assessments on production databases during non-peak times.
@@ -35,6 +35,6 @@ Do not install and run the Data Migration Assistant directly on the SQL Server
3535

3636
In addition, be sure that to provide the correct permissions to the shared folder to avoid migration failures. The correct permissions are specified in the tool. If a 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.
3737

38-
- 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, which 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.
38+
- 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, which is beneficial especially when migrating SQL logins. If SSL encryption isn't 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.
3939

4040
However, if all access involves a secure intranet configuration, encryption might not be required. Enabling encryption slows performance because the extra overhead that is required 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: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Run Data Migration Assistant from the command line (SQL Server) | Microsoft Docs"
33
description: Learn how to run Data Migration Assistant from the command line to assess SQL Server databases for migration
44
ms.custom: ""
5-
ms.date: "08/29/2018"
5+
ms.date: "10/20/2018"
66
ms.prod: sql
77
ms.prod_service: "dma"
88
ms.reviewer: ""
@@ -12,7 +12,7 @@ keywords: ""
1212
helpviewer_keywords:
1313
- "Data Migration Assistant, Command Line"
1414
ms.assetid: ""
15-
author: HJToland3
15+
author: pochiraju
1616
ms.author: rajpo
1717
manager: craigg
1818
---

‎docs/dma/dma-configurationsettings.md‎

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Configure settings for Data Migration Assistant (SQL Server) | Microsoft Docs"
33
description: Learn how to configure settings for the Data Migration Assistant by updating values in the configuration file
44
ms.custom: ""
5-
ms.date: "08/29/2018"
5+
ms.date: "10/20/2018"
66
ms.prod: sql
77
ms.prod_service: "dma"
88
ms.reviewer: ""
@@ -12,7 +12,7 @@ keywords: ""
1212
helpviewer_keywords:
1313
- "Data Migration Assistant, Assess"
1414
ms.assetid: ""
15-
author: HJToland3
15+
author: pochiraju
1616
ms.author: rajpo
1717
manager: craigg
1818
---
@@ -21,23 +21,23 @@ manager: craigg
2121

2222
You can fine-tune certain behavior of Data Migration Assistant by setting configuration values in the dma.exe.config file. This article describes key configuration values.
2323

24-
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.
24+
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.
2525

2626
- Desktop Application
2727

2828
%ProgramFiles%\\Microsoft Data Migration Assistant\\dma.exe.config
2929

30-
- Command Line Utility
30+
- Command-Line Utility
3131

3232
%ProgramFiles%\\Microsoft Data Migration Assistant\\dmacmd.exe.config
3333

3434
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.
3535

3636
## Number of databases to assess in parallel
3737

38-
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.
38+
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.
3939

40-
Starting with Data Migration Assistant v2.0, you can controll this by setting the parallelDatabases configuration value. Default value is 8.
40+
Starting with Data Migration Assistant v2.0, you can control this by setting the parallelDatabases configuration value. Default value is 8.
4141

4242
```
4343
<advisorGroup>
@@ -82,15 +82,15 @@ During assessment, Data Migration Assistant extracts data-tier application (dacp
8282
8383
- commandTimeout
8484

85-
This sets the IDbCommand.CommandTimeout property in *seconds*. (Default=60)
85+
This parameter sets the IDbCommand.CommandTimeout property in *seconds*. (Default=60)
8686

8787
- databaseLockTimeout
8888

89-
This is equivalent to [SET LOCK\_TIMEOUT timeout\_period ](../t-sql/statements/set-lock-timeout-transact-sql.md) in *milliseconds*. (Default=5000)
89+
This parameter is equivalent to [SET LOCK\_TIMEOUT timeout\_period](../t-sql/statements/set-lock-timeout-transact-sql.md) in *milliseconds*. (Default=5000)
9090

9191
- maxDataReaderDegreeOfParallelism
9292

93-
Number of SQL connection pool connections to use. (Default=8)
93+
This parameter sets the number of SQL connection pool connections to use. (Default=8)
9494

9595
```
9696
<advisorGroup>
@@ -105,11 +105,9 @@ maxDataReaderDegreeOfParallelism="8"/>
105105
</advisorGroup>
106106
```
107107

108-
109108
## Stretch Database: Recommendation threshold
110109

111-
With [SQL Server Stretch
112-
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.
110+
With [SQL Server Stretch 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.
113111

114112
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.
115113

@@ -128,8 +126,7 @@ Starting with Data Migration Assistant v2.0, you can control this threshold for
128126

129127
## SQL connection timeout
130128

131-
You can control the [SQL connection
132-
time-out](https://msdn.microsoft.com/library/system.data.sqlclient.sqlconnection.connectiontimeout(v=vs.110).aspx)
129+
You can control the [SQL connection time-out](https://msdn.microsoft.com/library/system.data.sqlclient.sqlconnection.connectiontimeout(v=vs.110).aspx)
133130
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.
134131

135132
```

‎docs/dma/dma-consolidatereports.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Assess an enterprise and consolidate assessment reports (SQL Server) | Microsoft Docs"
33
description: Learn how to use DMA to assess an enterprise and consolidate assessment reports before upgrading SQL Server or migrating to Azure SQL Database.
44
ms.custom: ""
5-
ms.date: "09/21/2018"
5+
ms.date: "10/20/2018"
66
ms.prod: sql
77
ms.prod_service: "dma"
88
ms.reviewer: ""
@@ -12,7 +12,7 @@ keywords: ""
1212
helpviewer_keywords:
1313
- "Data Migration Assistant, Assess"
1414
ms.assetid: ""
15-
author: HJToland3
15+
author: pochiraju
1616
ms.author: rajpo
1717
manager: craigg
1818
---
@@ -78,11 +78,11 @@ Create a database called **EstateInventory** and a table called **DatabaseInvent
7878

7979
![SQL Server table contents](../dma/media//dma-consolidatereports/dma-sql-server-table-contents.png)
8080

81-
If this database is not on the tools computer, ensure that the tools computer has network connectivity to this SQL Server instance.
81+
If this database isn't on the tools computer, ensure that the tools computer has network connectivity to this SQL Server instance.
8282

8383
The benefit of using a SQL Server table over a CSV file is that you can use the assessment flag column to control the instance / database that gets picked up for assessment, which makes it easier to separate assessments into smaller chunks. You can then span multiple assessments (see the section on running an assessment later in this article), which is easier than maintaining multiple CSV files.
8484

85-
Keep in mind that depending on the number of objects and their complexity, an assessment can take an exceptionally long time (hours+), so it is prudent to separate the assessment into manageable chunks.
85+
Keep in mind that depending on the number of objects and their complexity, an assessment can take an exceptionally long time (hours+), so it's prudent to separate the assessment into manageable chunks.
8686

8787
## Running a scaled assessment
8888
After loading the PowerShell modules into the modules directory and creating an inventory, you need to run a scaled assessment by opening PowerShell and running the dmaDataCollector function.
@@ -107,7 +107,7 @@ If there is an unexpected error, then the command window that gets initiated by
107107

108108
## Consuming the assessment JSON file
109109

110-
After your assessment has finished, you are now ready to import the data into SQL Server for analysis. To consume the assessment JSON file, open PowerShell and run the dmaProcessor function.
110+
After your assessment has finished, you're now ready to import the data into SQL Server for analysis. To consume the assessment JSON file, open PowerShell and run the dmaProcessor function.
111111

112112
![dmaProcessor function listing](../dma/media//dma-consolidatereports/dma-dmaProcessor-function-listing.png)
113113

@@ -116,12 +116,12 @@ The parameters associated with the dmaProcessor function are described in the fo
116116
|Parameter |Description
117117
|---------|---------|
118118
|**processTo** | The location to which the JSON file will be processed. Possible values are **SQLServer** and **AzureSQLDatabase**. |
119-
|**serverName** | The SQL Server instance to which data will be processed. If you specify **AzureSQLDatabase** for the **processTo** parameter, then include only the SQL Server name (do not include .database.windows.net). You will be prompted for two logins when targeting Azure SQL Database; the first is your Azure tenant credentials, while the second is your admin login for the Azure SQL Server. |
120-
|**CreateDMAReporting** | The staging database to create for processing the JSON file. If the database you specify already exists and you set this parameter to one, then objects do not get created. This parameter is useful for recreating a single object that has been dropped. |
119+
|**serverName** | The SQL Server instance to which data will be processed. If you specify **AzureSQLDatabase** for the **processTo** parameter, then include only the SQL Server name (don't include .database.windows.net). You'll be prompted for two logins when targeting Azure SQL Database; the first is your Azure tenant credentials, while the second is your admin login for the Azure SQL Server. |
120+
|**CreateDMAReporting** | The staging database to create for processing the JSON file. If the database you specify already exists and you set this parameter to one, then objects don't get created. This parameter is useful for recreating a single object that has been dropped. |
121121
|**CreateDataWarehouse** | Creates the data warehouse that will be used by the Power BI report. |
122122
|**databaseName** | The name of the DMAReporting database. |
123123
|**warehouseName** | The name of the data warehouse database. |
124-
|**jsonDirectory** | The directory containing the JSON assessment file. If there are multiple JSON files in the directory, then they are processed one by one. |
124+
|**jsonDirectory** | The directory containing the JSON assessment file. If there are multiple JSON files in the directory, then they're processed one by one. |
125125

126126
The dmaProcessor function should only take a few seconds to process a single file.
127127

@@ -130,14 +130,14 @@ After the dmaProcessor has finishing processing the assessment files, the data w
130130

131131
1. Use the LoadWarehouse script to populate any missing values in the dimensions.
132132

133-
The script will take the data from the ReportData table in the DMAReporting database and load it into the warehouse. If there are any errors during this load process, they are likely a result of missing entries in the dimension tables.
133+
The script will take the data from the ReportData table in the DMAReporting database and load it into the warehouse. If there are any errors during this load process, they're likely a result of missing entries in the dimension tables.
134134

135135
2. Load the data warehouse.
136136

137137
![LoadWarehouse contents loaded](../dma/media//dma-consolidatereports/dma-LoadWarehouse-loaded.png)
138138

139139
## Set your database owners
140-
While it is not mandatory, to get the most value from the reports, it is recommended that you set the database owners in the **dimDBOwner** dimension, and then update **DBOwnerKey** in the **FactAssessment** table. Following this process will allow slicing and filtering the Power BI report based on specific database owners.
140+
While it's not mandatory, to get the most value from the reports, it's recommended that you set the database owners in the **dimDBOwner** dimension, and then update **DBOwnerKey** in the **FactAssessment** table. Following this process will allow slicing and filtering the Power BI report based on specific database owners.
141141

142142
You can also use the LoadWarehouse script to provide the basic TSQL statements for you to set the database owners.
143143

@@ -153,7 +153,7 @@ You can also use the LoadWarehouse script to provide the basic TSQL statements f
153153
154154
![DMA Reports Power BI template loaded](../dma/media//dma-consolidatereports/dma-reports-powerbi-template-loaded.png)
155155

156-
After the report has refreshed the data from the **DMAWarehouse** database, you are presented with a report similar to the following.
156+
After the report has refreshed the data from the **DMAWarehouse** database, you're presented with a report similar to the following.
157157

158158
![DMAWarehouse report view](../dma/media//dma-consolidatereports/dma-DMAWarehouse-report.png)
159159

0 commit comments

Comments
 (0)