You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: 'This guide teaches you to migrate your Microsoft Access databases to Microsoft SQL Server by using SQL Server Migration for Access (SSMA for Access). '
3
+
description: 'In this guide, you learn how to migrate your Microsoft Access databases to Microsoft SQL Server by using SQL Server Migration for Access.'
To migrate your Access database to SQL Server, you need:
19
+
In this guide, you learn how to migrate your Microsoft Access databases to SQL Server by using SQL Server Migration for Access (SSMA for Access).
25
20
26
-
- To verify your source environment is supported.
27
-
-[SQL Server Migration Assistant for Access](https://www.microsoft.com/download/details.aspx?id=54255).
28
-
- Connectivity and sufficient permissions to access both source and target.
21
+
For other migration guides, see [Azure Database Migration Guides](https://datamigration.microsoft.com/).
29
22
23
+
## Prerequisites
30
24
31
-
## Pre-migration
25
+
Before you begin migrating your Access database to SQL Server:
32
26
27
+
- Verify that your source environment is supported.
28
+
- Have [SSMA for Access](https://www.microsoft.com/download/details.aspx?id=54255).
29
+
- Have connectivity and sufficient permissions to access both the source and target.
33
30
34
-
After you have met the prerequisites, you are ready to discover the topology of your environment and assess the feasibility of your migration.
31
+
## Pre-migration
35
32
33
+
After you've met the prerequisites, you're ready to discover the topology of your environment and assess the feasibility of your migration.
36
34
37
35
### Assess
38
36
39
-
Use SQL Server Migration Assistant (SSMA) for Access to review database objects and data, and assess databases for migration. To learn more about the tool, see [SQL Server Migration Assistant for Access](/sql/ssma/access/sql-server-migration-assistant-for-access-accesstosql).
37
+
By using SSMA for Access, you can review database objects and data and assess databases for migration. To learn more about the tool, see [SQL Server Migration Assistant for Access](/sql/ssma/access/sql-server-migration-assistant-for-access-accesstosql).
40
38
41
-
To create an assessment, follow these steps:
39
+
To create an assessment:
42
40
43
-
1. Open [SQL Server Migration Assistant for Access](https://www.microsoft.com/download/details.aspx?id=54255).
44
-
1. Select **File** and then choose**New Project**.
45
-
1.Provide a project name, a location to save your project, and then select a SQL Server migration target from the drop-down. Select **OK**:
41
+
1. Open [SSMA for Access](https://www.microsoft.com/download/details.aspx?id=54255).
42
+
1. Select **File**, and then select**New Project**.
43
+
1.Enter a project name and a location to save your project. Then select a SQL Server migration target from the drop-down list, and select **OK**.
52
50
53
-
1. In **Access Metadata Explorer**, right-click the database you want to assess, and then choose**Create report**. Alternatively, you can choose **Create report** from the navigation bar after selecting the schema:
51
+
1. In **Access Metadata Explorer**, right-click the database you want to assess and then select**Create Report**. Alternatively, you can select the schema and then select the **Create Report** tab.
56
54
57
55
1. Review the HTML report to understand conversion statistics and any errors or warnings. You can also open the report in Excel to get an inventory of Access objects and the effort required to perform schema conversions. The default location for the report is in the report folder within SSMAProjects.
58
56
59
-
For example: `drive:\<username>\Documents\SSMAProjects\MyAccessMigration\report\report_2020_11_12T02_47_55\`
57
+
For example, see `drive:\<username>\Documents\SSMAProjects\MyAccessMigration\report\report_2020_11_12T02_47_55\`.
72
69
73
-
1. You can change the type mapping for each table by selecting the table in the **Oracle Metadata explorer**.
70
+
1. You can change the type mapping for each table by selecting the table in **Access Metadata Explorer**.
74
71
72
+
### Convert
75
73
76
-
### Convert
74
+
To convert database objects:
77
75
78
-
To convert database objects, follow these steps:
76
+
1. Select **Connect to SQL Server**, and enter connection details.
79
77
80
-
1. Select **Connect to SQL Server** and provide connection details:
78
+
81
79
82
-
80
+
1. Right-click the database in **Access Metadata Explorer**, and select **Convert Schema**. Alternatively, you can select your database and then select the **Convert Schema** tab.
83
81
84
-
1. Right-click the database in **Access Metadata Explorer** and choose **Convert schema**. Alternatively, you can choose **Convert schema** from the top line navigation bar after choosing your database:
82
+
85
83
86
-
84
+
1. After the conversion completes, compare and review the converted objects to the original objects to identify potential problems and address them based on the recommendations.
87
85
88
-
1. After the conversion completes, compare and review the converted objects to the original objects to identify potential problems and address them based on the recommendations:
86
+
1. (Optional) To convert an individual object, right-click the object and select **Convert Schema**. An object that has been converted appears bold in **Access Metadata Explorer**.
95
93
96
-
1. (Optional) To convert an individual object, right-click the object and choose **Convert schema**. An object that has been converted appears bold in the **Access Metadata Explorer**:
97
-
98
-
94
+
99
95
100
-
1. Select **Review results** in the Output pane, and review errors in the **Error list** pane.
101
-
1. Save the project locally for an offline schema remediation exercise. Select **Save Project** from the **File** menu. This gives you an opportunity to evaluate the source and target schemas offline and perform remediation before you can publish the schema to SQL Server.
102
-
96
+
1. In the output pane, select **Review results**, and review the errors in the **Error List** pane.
97
+
1. Save the project locally for an offline schema remediation exercise. On the **File** menu, select **Save Project**. This step gives you an opportunity to evaluate the source and target schemas offline and perform remediation before you publish the schema to SQL Server.
103
98
104
99
## Migrate
105
100
106
-
After you have completed assessing your databases and addressing any discrepancies, the next step is to execute the migration process. Migrating data is a bulk-load operation that moves rows of data into SQL Server in transactions. The number of rows to be loaded into SQL Server in each transaction is configured in the project settings.
107
-
108
-
To publish your schema and migrate the data using SSMA for Access, follow these steps:
109
-
110
-
1. If you haven't already, select **Connect to SQL Server** and provide connection details.
101
+
After you've assessed your databases and addressed any discrepancies, the next step is to run the migration process. Migrating data is a bulk-load operation that moves rows of data into SQL Server in transactions. The number of rows to be loaded into SQL Server in each transaction is configured in the project settings.
111
102
112
-
1. Publish the schema: Right-click the database from the **SQL Server Metadata Explorer**and choose **Synchronize with Database**. This action publishes the MySQL schema to SQL Server:
103
+
To publish your schemaand migrate the data by using SSMA for Access:
113
104
114
-
105
+
1. If you haven't already, select **Connect to SQL Server** and enter connection details.
115
106
116
-
Review the mapping between your source project and your target:
107
+
1. Publish the schema by right-clicking the database in **SQL Server Metadata Explorer**and selecting **Synchronize with Database**. This action publishes the MySQL schema to SQL Server.
117
108
118
-
109
+
119
110
120
-
1.Migrate the data: Right-click the database or object you want to migrate in **Access Metadata Explorer**, and choose **Migrate data**. Alternatively, you can select **Migrate Data** from the top-line navigation bar. To migrate data for an entire database, select the check box next to the database name. To migrate data from individual tables, expand the database, expand Tables, and then select the check box next to the table. To omit data from individual tables, clear the check box:
111
+
1.Review the mapping between your source project and your target.
123
114
124
-
1.After migration completes, view the **Data Migration Report**:
115
+
1.Migrate the data by right-clicking the database or object you want to migrate in **Access Metadata Explorer** and selecting **Migrate Data**. Alternatively, you can select the **Migrate Data** tab. To migrate data for an entire database, select the check box next to the database name. To migrate data from individual tables, expand the database, expand **Tables**, and then select the check boxes next to the tables. To omit data from individual tables, clear the check boxes.
125
116
126
-
117
+
127
118
128
-
1.Connect to your SQL Server instance by using [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) and validate the migration by reviewing the data and schema:
119
+
1.After migration is completed, view the **Data Migration Report**.
129
120
130
-
121
+
131
122
123
+
1. Connect to your SQL Server instance by using [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms), and validate the migration by reviewing the data and schema.
132
124
125
+
133
126
134
-
## Post-migration
127
+
## Post-migration
135
128
136
-
After you have successfully completed the **Migration** stage, you need to go through a series of post-migration tasks to ensure that everything is functioning as smoothly and efficiently as possible.
129
+
After you've successfully completed the *migration* stage, you need to complete a series of post-migration tasks to ensure that everything is functioning as smoothly and efficiently as possible.
137
130
138
131
### Remediate applications
139
132
140
-
After the data is migrated to the target environment, all the applications that formerly consumed the source need to start consuming the target. Accomplishing this will in some cases require changes to the applications.
133
+
After the data is migrated to the target environment, all the applications that formerly consumed the source need to start consuming the target. Accomplishing this task will require changes to the applications in some cases.
141
134
142
135
### Perform tests
143
136
144
-
The test approach for database migration consists of performing the following activities:
145
-
146
-
1.**Develop validation tests**. To test database migration, you need to use SQL queries. You must create the validation queries to run against both the source and the target databases. Your validation queries should cover the scope you have defined.
147
-
148
-
2.**Set up test environment**. The test environment should contain a copy of the source database and the target database. Be sure to isolate the test environment.
149
-
150
-
3.**Run validation tests**. Run the validation tests against the source and the target, and then analyze the results.
151
-
152
-
4.**Run performance tests**. Run performance test against the source and the target, and then analyze and compare the results.
137
+
The test approach for database migration consists of the following activities:
153
138
139
+
1.**Develop validation tests**: To test database migration, you need to use SQL queries. You must create the validation queries to run against both the source and the target databases. Your validation queries should cover the scope you've defined.
140
+
2.**Set up a test environment**: The test environment should contain a copy of the source database and the target database. Be sure to isolate the test environment.
141
+
3.**Run validation tests**: Run validation tests against the source and the target, and then analyze the results.
142
+
4.**Run performance tests**: Run performance tests against the source and the target, and then analyze and compare the results.
154
143
155
144
### Optimize
156
145
157
-
The post-migration phase is crucial for reconciling any data accuracy issues and verifying completeness, as well as addressing performance issues with the workload.
146
+
The post-migration phase is crucial for reconciling any data accuracy issues, verifying completeness, and addressing performance issues with the workload.
158
147
159
148
> [!Note]
160
-
> For additional detail about these issues and specific steps to mitigate them, see the [Post-migration Validation and Optimization Guide](../../../relational-databases/post-migration-validation-and-optimization-guide.md).
149
+
> For more information about these issues and the steps to mitigate them, see the [Post-migration validation and optimization guide](../../../relational-databases/post-migration-validation-and-optimization-guide.md).
161
150
162
-
## Migration assets
151
+
## Migration assets
163
152
164
-
For additional assistance with completing this migration scenario, please see the following resources, which were developed in support of a real-world migration project engagement.
153
+
For more assistance with completing this migration scenario, see the following resource. It was developed in support of a real-world migration project engagement.
165
154
166
155
|**Title/link**|**Description**|
167
156
| -------------- | --------------- |
168
-
|[Data Workload Assessment Model and Tool](https://github.com/Microsoft/DataMigrationTeam/tree/master/Data%20Workload%20Assessment%20Model%20and%20Tool)| This tool provides suggested “best fit” target platforms, cloud readiness, and application/database remediation level for a given workload. It offers simple, one-click calculation and report generation that greatly helps to accelerate large estate assessments by providing and automated and uniform target platform decision process. |
157
+
|[Data Workload Assessment Model and Tool](https://github.com/Microsoft/DataMigrationTeam/tree/master/Data%20Workload%20Assessment%20Model%20and%20Tool)| This tool provides suggested "best fit" target platforms, cloud readiness, and application or database remediation level for a given workload. It offers simple, one-click calculation and report generation that helps to accelerate large estate assessments by providing an automated and uniform target platform decision process. |
169
158
170
-
These resources were developed as part of the Data SQL Ninja Program, which is sponsored by the Azure Data Group engineering team. The core charter of the Data SQL Ninja program is to unblock and accelerate complex modernization and compete data platform migration opportunities to Microsoft's Azure Data platform. If you think your organization would be interested in participating in the Data SQL Ninja program, please contact your account team and ask them to submit a nomination.
159
+
The preceding resource was developed by the Data SQL Engineering team. A core charter of this team is to unblock and accelerate complex modernization and complete data platform migration projects to the Microsoft Azure Data platform.
171
160
172
161
## Next steps
173
162
174
-
After migration, review the [Post-migration validation and optimization guide](/sql/relational-databases/post-migration-validation-and-optimization-guide).
175
-
176
-
For a matrix of the Microsoft and third-party services and tools that are available to assist you with various database and data migration scenarios, as well as specialty tasks, see [Data migration services and tools](/azure/dms/dms-tools-matrix).
177
-
178
-
For other migration guides, see [Database Migration](https://datamigration.microsoft.com/).
179
-
180
-
For video content, see:
181
-
-[Overview of the migration journey](https://azure.microsoft.com/resources/videos/overview-of-migration-and-recommended-tools-services/)
163
+
- After migration, review the [Post-migration validation and optimization guide](/sql/relational-databases/post-migration-validation-and-optimization-guide).
164
+
- For a matrix of Microsoft and third-party services and tools that are available to assist you with various database and data migration scenarios and specialty tasks, see [Data migration services and tools](/azure/dms/dms-tools-matrix).
165
+
- For other migration guides, see [Azure Database Migration Guides](https://datamigration.microsoft.com/).
166
+
- For video content, see [Overview of the migration journey](https://azure.microsoft.com/resources/videos/overview-of-migration-and-recommended-tools-services/).
0 commit comments