Skip to content

Commit d21473a

Browse files
committed
edits per review
1 parent c505e1a commit d21473a

7 files changed

Lines changed: 21 additions & 21 deletions

docs/dma/dma-commandline.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ DmaCmd.exe /AssessmentName="string"
5555
|`/FeatureDiscoveryReportJson` | Path to the feature discovery JSON report. If this file is generated, then it can be used to run target readiness assessment again without connecting to source. | N
5656
|`/ImportFeatureDiscoveryReportJson` | Path to the feature discovery JSON report created earlier. Instead of source connections, this file will be used. | N
5757
|`/EnableAssessmentUploadToAzureMigrate` | Enables uploading and publishing assessment results to Azure Migrate | N
58-
|`/AzureCloudEnvironment` |Selects the Azure cloud environment to connect to, default is Azure Public Cloud. Supported values: Azure (default), AzureChina, AzureGermany,AzureUSGovernment. | N
58+
|`/AzureCloudEnvironment` |Selects the Azure cloud environment to connect to, default is Azure Public Cloud. Supported values: Azure (default), AzureChina, AzureGermany, AzureUSGovernment. | N
5959
|`/SubscriptionId` |Azure subscription ID. | Y <br> (Required if EnableAssessmentUploadToAzureMigrate argument is specified)
6060
|`/AzureMigrateProjectName` |The Azure Migrate Project name to upload assessment results to. | Y <br> (Required if EnableAssessmentUploadToAzureMigrate argument is specified)
6161
|`/ResourceGroupName` |Azure Migrate resource group name. | Y <br> (Required if EnableAssessmentUploadToAzureMigrate argument is specified)
@@ -299,7 +299,7 @@ These commands support recommendations for both Azure SQL Database single databa
299299
|`/SkuRecommendationSubscriptionId` | The subscription ID. | Y <br> (For the latest prices)
300300
|`/SkuRecommendationDatabasesToRecommend` | Space-separated list of databases to recommend for (e.g. “Database1” “Database2” “Database3”). Names are case-sensitive and must be surrounded by double-quotes. If omitted, recommendations are provided for all databases. | N
301301
|`/AzureAuthenticationTenantId` | The authentication tenant. | Y <br> (For the latest prices)
302-
|`/AzureAuthenticationClientId` | The client ID of the AAD app used for authentication. | Y <br> (For the latest prices)
302+
|`/AzureAuthenticationClientId` | The client ID of the Azure AD app used for authentication. | Y <br> (For the latest prices)
303303
|`/AzureAuthenticationInteractiveAuthentication` | Set to true to pop up the window. | Y <br> (For the latest prices) <br>(Pick one of the 3 authentication options - option 1)
304304
|`/AzureAuthenticationCertificateStoreLocation` | Set to the certificate store location (e.g. "CurrentUser"). | Y <br>(For the latest prices) <br> (Pick one of the 3 authentication options - option 2)
305305
|`/AzureAuthenticationCertificateThumbprint` | Set to the cert thumbprint. | Y <br> (For the latest prices) <br>(Pick one of the 3 authentication options - option 2)

docs/ssdt/database-project-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ The Extended Verification feature can also be used when developing an applicatio
146146
147147
2. In **Properties**, change the **Extended T-SQL Verification** property to **False**.
148148

149-
![File Properties](../ssdt/media/ssdt-evf.gif "File Properties")
149+
![File Properties](../ssdt/media/ssdt-evf.gif "File Properties")
150150

151151
### Special Considerations for Collations
152152
For more information regarding collations in partially contained databases, see [Contained Database Collations](https://msdn.microsoft.com/library/ff929080%28v=sql.110%29.aspx).

docs/ssma/access/connecting-to-azure-sql-db-accesstosql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ Your connection to SQL Azure stays active until you close the project. When you
9090

9191
The procedure for reconnecting to SQL Azure is the same as the procedure for establishing a connection.
9292

93-
## Next Step
93+
## Next steps
9494
The next step in the migration depends on your project needs:
9595

9696
- To customize the mapping between Access schemas and Azure SQL Database, see [Mapping Access Databases to SQL Server Schemas](mapping-source-and-target-databases-accesstosql.md).

docs/ssma/access/converting-access-database-objects-accesstosql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ After you convert Access metadata to [!INCLUDE[ssNoVersion](../../includes/ssnov
109109

110110
You can now view the changes in the code on the **SQL** tab.
111111

112-
## Next Step
112+
## Next steps
113113
The next step in the migration process is [load converted database objects into SQL Server](loading-converted-database-objects-into-sql-server-accesstosql.md)
114114

115115
## See Also

docs/ssma/access/executing-the-ssma-console-accesstosql.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -396,7 +396,7 @@ or
396396

397397
migrate-data
398398

399-
1. Migrates the source data to the target.
399+
- Migrates the source data to the target.
400400

401401
**Script**
402402

@@ -540,27 +540,27 @@ The default console output setting for the migration commands is 'Full' output r
540540

541541
synchronize-target
542542

543-
1. Synchronizes the target objects with the target database.
543+
- Synchronizes the target objects with the target database.
544544

545-
2. If this command is executed against the source database, you get an error.
545+
- If this command is executed against the source database, you get an error.
546546

547-
3. If the target database connection is not performed before executing this command or the connection to the target database server fails during the command execution, an error is generated and the console application exits.
547+
- If the target database connection is not performed before executing this command or the connection to the target database server fails during the command execution, an error is generated and the console application exits.
548548

549549
**Script**
550550

551-
1. `object-name:` Specifies the target object(s) considered for synchronizing with target database (It can have individual object names or a group object name).
551+
- `object-name:` Specifies the target object(s) considered for synchronizing with target database (It can have individual object names or a group object name).
552552

553-
2. `object-type:` Specifies the type of the object specified in the object-name attribute (if object category is specified then object type will be "category").
553+
- `object-type:` Specifies the type of the object specified in the object-name attribute (if object category is specified then object type will be "category").
554554

555-
3. `on-error:` Specifies whether to specify synchronization errors as warnings or error. Available options for on-error:
555+
- `on-error:` Specifies whether to specify synchronization errors as warnings or error. Available options for on-error:
556556

557557
- report-total-as-warning
558558

559559
- report-each-as-warning
560560

561561
- fail-script
562562

563-
4. `report-errors-to:` Specifies location of error report for the synchronization operation (optional attribute) if only folder path is given, then file by name **TargetSynchronizationReport.XML** is created.
563+
- `report-errors-to:` Specifies location of error report for the synchronization operation (optional attribute) if only folder path is given, then file by name **TargetSynchronizationReport.XML** is created.
564564

565565
**Syntax Example:**
566566

@@ -616,19 +616,19 @@ refresh-from-database
616616

617617
Requires one or several metabase nodes as command line parameter.
618618

619-
1. `object-name:` Specifies the source object(s) considered for refreshing from source database (It can have individual object names or a group object name).
619+
- `object-name:` Specifies the source object(s) considered for refreshing from source database (It can have individual object names or a group object name).
620620

621-
2. `object-type:` Specifies the type of the object specified in the object-name attribute (if object category is specified then object type will be "category").
621+
- `object-type:` Specifies the type of the object specified in the object-name attribute (if object category is specified then object type will be "category").
622622

623-
3. `on-error:` Specifies whether to specify refresh errors as warnings or error. Available options for on-error:
623+
- `on-error:` Specifies whether to specify refresh errors as warnings or error. Available options for on-error:
624624

625625
- report-total-as-warning
626626

627627
- report-each-as-warning
628628

629629
- fail-script
630630

631-
4. `report-errors-to:` Specifies location of error report for the refresh operation (optional attribute) if only folder path is given, then file by name **SourceDBRefreshReport.XML** is created.
631+
- `report-errors-to:` Specifies location of error report for the refresh operation (optional attribute) if only folder path is given, then file by name **SourceDBRefreshReport.XML** is created.
632632

633633
**Syntax Example:**
634634

@@ -726,7 +726,7 @@ or
726726
</save-as-script>
727727
```
728728

729-
## Next Steps
729+
## Next steps
730730

731731
For information on command line options, see [Command Line Options in SSMA Console &#40;AccessToSQL&#41;](../../ssma/access/command-line-options-in-ssma-console-accesstosql.md) .
732732

docs/ssma/access/migration-wizard-accesstosql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ On the Connect to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] page
7575
> As soon as the connection succeeds, you will encounter **Link Tables** page where you have an option of linking the tables. Click **Next** and the migration starts.
7676
7777
## Connect to SQL Azure Page
78-
On the Connect to SQL Azure page, you specify connection properties, and then connect to SQL Azure. To create a new azure database, you can do so by using **Create Azure Database** option that appears on the click of **Browse** button. For more information, see [Connect to SQL Azure](connect-to-azure-sql-db-accesstosql.md)
78+
On the Connect to SQL Azure page, you specify connection properties, and then connect to SQL Azure. To create a new Azure database, you can do so by using **Create Azure Database** option that appears on the click of **Browse** button. For more information, see [Connect to SQL Azure](connect-to-azure-sql-db-accesstosql.md)
7979

8080
> [!IMPORTANT]
8181
> As soon as the connection succeeds, you will encounter **Link Tables** page where you have an option of linking the tables. Click **Next** button on the Links page to start migration.

docs/ssma/mysql/mapping-mysql-and-sql-server-data-types-mysqltosql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,9 +62,9 @@ When you view the **Type Mapping** tab in SSMA, the background is color-coded to
6262

6363
This lets you customize the data mapping for smaller and larger values of the same data type. Under **Target type**, select the target SQL Server or SQL Azure data type.
6464

65-
1. Some types require a target data type length. If required, enter the new data length in the **Replace With** box, and then click **OK**.
65+
- Some types require a target data type length. If required, enter the new data length in the **Replace With** box, and then click **OK**.
6666

67-
2. Some types require a target data type **precision** and **scale**. If required, enter the new precision and scale in the **Replace With** box, and then click **OK**.
67+
- Some types require a target data type **precision** and **scale**. If required, enter the new precision and scale in the **Replace With** box, and then click **OK**.
6868

6969
- **To remove a data type mapping, do the following:**
7070

0 commit comments

Comments
 (0)