Skip to content

Commit d9d0052

Browse files
TimShererWithAquentTimShererWithAquent
committed
Additional edits.
1 parent c4f080f commit d9d0052

2 files changed

Lines changed: 6 additions & 6 deletions

File tree

‎docs/dea/database-experimentation-assistant-run-command-prompt.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -75,13 +75,13 @@ If you're using Distributed Replay, perform the following steps.
7575

7676
b. Run `Set @durationInMins=0` so that the trace capture doesn't stop automatically after a specified time.
7777

78-
c. To set the maximum file size per trace file, run `Set @maxfilesize`. The recommended size is 200, in MB.
78+
c. To set the maximum file size per trace file, run `Set @maxfilesize`. The recommended size is 200 MB.
7979

8080
d. Edit `@Tracefile` to set a unique name for your trace file.
8181

8282
e. Edit `@dbname` to specify a database name if the workload must be captured only on a specific database. By default, the workload on the entire server is captured.
8383

84-
4. To replay the IRF file against the target SQL Server instance, at a command prompt, run the following command:
84+
4. To replay the IRF file against the target SQL Server instance, run the following command:
8585

8686
```cmd
8787
DReplay replay -m "dreplaycontroller" -d "<Folder Path on Dreplay Controller>\IrfFolder" -o -s "SQL2016Target" -w "dreplaychild1,dreplaychild2,dreplaycild3,dreplaychild4"
@@ -106,7 +106,7 @@ If you're using Distributed Replay, perform the following steps.
106106
107107
## Using InBuilt Replay
108108
109-
If you're using InBuilt Replay, you won't have to set up Distributed Replay. The ability to use InBuilt Replay by using the command line is on the way. Currently, you can use our GUI to run replay using InBuilt Replay.
109+
If you're using InBuilt Replay, you won't have to set up Distributed Replay. The ability to use InBuilt Replay at the command prompt is on the way. Currently, you can use our GUI to run replay using InBuilt Replay.
110110
111111
## Analyze traces using the DEA command
112112
@@ -128,8 +128,8 @@ When analyzing traces using the DEA command, you can use the following options:
128128

129129
| Option| Description |
130130
| --- | --- |
131-
| `-a`, `--traceA` | Required. File path to the event file for A instance. Example: *C:\traces\Sql2008trace.trc*. If there's a batch of files, select the first file and DEA checks for rollover files automatically. If files are in blob, provide the folder path where you want the event files stored locally. Example: *C:\traces\\* |
132-
| `-b`, `--traceB` | Required. File path to the event file for B instance. Example: *C:\traces\Sql2014trace.trc*. If there's a batch of files, select the first file and DEA checks for rollover files automatically. If files are in blob, provide the folder path where you want the event files stored locally. Example: *C:\traces\\* |
131+
| `-a`, `--traceA` | Required. File path to the event file for the A instance. Example: *C:\traces\Sql2008trace.trc*. If there's a batch of files, select the first file and DEA checks for rollover files automatically. If files are in blob, provide the folder path where you want the event files stored locally. Example: *C:\traces\\* |
132+
| `-b`, `--traceB` | Required. File path to the event file for the B instance. Example: *C:\traces\Sql2014trace.trc*. If there's a batch of files, select the first file and DEA checks for rollover files automatically. If files are in blob, provide the folder path where you want the event files stored locally. Example: *C:\traces\\* |
133133
| `-r`, `--ReportName` | Required. Name for current analysis. The analysis report that gets generated is identified by this name. |
134134
| `-t`, `--type` | Default: 0. Type of the SQL Server (SqlServer = 0, AzureSQLDB = 1, Azure SQL Managed Instance = 2). |
135135
| `-h`, `--host` | Required. SQL Server host name or instance name. |

‎docs/dma/dma-assess-app-data-layer.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ To enable this assessment, use the Data Access Migration Toolkit (DAMT), a Visua
8585

8686
![Screenshot shows Data Access Migration with an application database selected.](../dma/media/dma-assess-app-data-layer/dma-select-app-database.png)
8787

88-
To facilitate data access assessment, DMA introduces the ability to include JSON files with application queries. Next, include the JSON file we created earlier with the application queries.
88+
To facilitate data access assessment, DMA introduces the ability to include JSON files with application queries. Next, include the JSON file created earlier with the application queries.
8989

9090
11. Select the database and browse to the JSON file exported from Data Access Migration Toolkit to include the queries from the application for the assessment.
9191

0 commit comments

Comments
 (0)