Fix SSMA for Access When It Finds No Tables to Convert
Question details
The user needs SSMA for Access to detect tables in a back-end database so they can migrate them to SQL Server.

- Product
- SQL Server Migration Assistant for Access and Microsoft Access 2007
- Device & OS
- not provided
- Scenario
- An Access database was converted from Access 2003 format and split into front-end and back-end files before migration.
- Observed behavior
- SSMA for Access does not detect tables in the back-end database and shows nothing to convert.
Open the back-end file in Access and confirm that its tables contain the expected data. Identify the SQL Server instance and destination database you will use for the migration.
Import the tables into a new Access database for SSMA
Use a fresh Access database as the SSMA source when tables in the existing back-end file are not detected.
In Access, click the Office Button, select New, and create a blank database.
On the External Data tab, select Access. Browse to the back-end file, choose to import tables into the current database, and select the tables in the import dialog.
Open the imported tables from the Navigation Pane and confirm that their data is present.
In SSMA for Access, create or open a project, add the new Access database, and check the Access Metadata Explorer for its tables.
Connect to the target SQL Server database, select the imported tables, and use Convert Schema. Review the results, synchronize the schema with SQL Server, and then migrate the data.

Import Access tables directly into SQL Server
Use the SQL Server Import and Export Wizard as a workaround if SSMA still cannot detect the tables.
Use WPS Office for Everyday Office Files
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make moving everyday files straightforward. It does not replace SSMA or migrate Access databases to SQL Server.

Frequently Asked Questions
Which Access file should I use as the migration source?
For a split database, open the back-end file in Access and confirm that it contains the actual tables and data. Use that file when importing tables into a new database or choosing the source in the import wizard.
What if SSMA still finds no tables in the new database?
Confirm that the tables appear in the new database's Navigation Pane and that SSMA has opened that file. If they are still not detected, try Tasks > Import Data on a SQL Server destination database.
Why is the Access provider missing from the import wizard?
The required Access Database Engine provider may not be installed or may not match the wizard's 32-bit or 64-bit architecture. Install or use a compatible provider and restart the wizard.
Will importing tables also recreate all relationships and indexes?
Do not assume the import wizard will recreate every schema detail. After importing, inspect the tables in SQL Server Management Studio and add or adjust relationships, indexes, and other properties as needed.




