Access
SQL Server

Access to SQL Server

Conversion and Synchronization

Why Migrate from Access?

MS Access is a popular desktop database widely used in organizations. In time, most Access databases grow in size and complexity. When Access databases are becoming unstable and slow due to large amounts of data, it's time to consider migrating from Access to SQL Server.

Time to Upgrade?

When your Access database reaches 300MB or serves more than 20 concurrent users, SQL Server provides the scalability and performance your growing business needs.

Scale Your Data

MS Access vs SQL Server

Compare capabilities and limitations

Microsoft Access SQL Server
Size Limitations: Microsoft advertises that MS Access has a size limit of 2 GB, but in fact, you will notice a performance and stability degradation above about 300 MB.
Unlimited Scale: The SQL Server database usually performs much better than an Access database, especially with large, terabyte-sized databases.
User Limit: Microsoft says the Access database cannot support more than 255 concurrent users. Actually, MS Access applications are NOT designed to support about 20 or more concurrent users on a LAN.
Massive Concurrency: By default, SQL Server allows a maximum of 32,767 concurrent connections. SQL Server processes queries much faster and efficiently by processing queries in parallel, using multiple native threads.
Internet Limitations: MS Access applications are NOT designed to be exposed to the Internet. Workarounds like Remote Desktop Connection are expensive to build and maintain with poor performance.
Internet Ready: SQL Server can be easily configured for accessing over the Internet. Employees, partners, and customers can exchange information and update it in real-time, wherever there is Internet access.
Stability Issues: Overgrown Access databases can often crash and become corrupted. Built-in limitations restrict 24/7 operation.
Enterprise Reliability: In case of system crash or power outage, SQL Server can automatically restore the database to a consistent state in minutes without administrator intervention.

Migrate Access to SQL Server

Take your database to the next level

So when it's time for your Access database to take it to the next level, you can upgrade to SQL Server, which supports larger amounts of data, more concurrent users, and more capacity (on-premises or in the Azure cloud).

It would be an obvious choice to migrate overgrown Access databases to SQL Server as they are all produced by the same vendor.

Cloud Migration Options

For large data storage volumes with many clients, consider migrating to cloud-based solutions for enhanced scalability and accessibility.

Why use DBConvert SQL Migration tools?

Designed for large and complex database migrations

Our SQL migration tools are designed to convert and synchronize large and complex databases. Data can be migrated between local and remote databases as:

MS Access
(.MDB or .ACCDB)
SQL Server
On-premises
Azure SQL
Cloud Database
Google Cloud
Cloud SQL Server
Amazon RDS
SQL Server

Automatic Query Conversion

DBConvert software can automatically convert MS Access queries to SQL Server views. There is no need to know the differences between SQL dialects.

Sync Access to SQL Server

Phased migration approach for minimal disruption

The Expensive Way

Trying to rewrite the entire system at once is the EXPENSIVE way to convert data from Access to SQL Server. In most cases, developing the target SQL Server requires more work than just creating a new database from scratch.

The Right Way - Phased Approach

In the early stages, legacy Access databases are often maintained for some time, with updated data flowing into both Access databases and SQL Server databases.

DBSync Solution

DBSync for Access and SQL Server is designed to synchronize data between Access and SQL Server databases.

Insert, Update, and Drop synchronization types give strong consistency between Source and Target databases.

Important Notes

Please keep these considerations in mind

1

Table Requirements

Make sure every Access table has an index and a primary key. SQL Server requires all tables to have at least one index, and the linked table must have a primary key if the table can be updated.

2

Conversion Scope

Forms, reports, macros, and VBA modules are not converted. Only data structure and content are migrated.

3

Migration Time

Please be patient. The migration process can take a long time, depending on the size of the database objects and the amount of data that needs to be transferred.

Using Access to SQL Server Tools

When launching the DBConvert or DBSync application in GUI mode, it seamlessly guides you through the steps to initiate database migration or synchronization:

1

Connect to Access source database

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to Access source database from DBConvert
2

Connect to SQL Server destination database

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to SQL Server target database from DBConvert

NOTE #1

Each DBConvert or DBSync tool's name comprises two different databases, enabling any specified database to operate as the source or destination. Furthermore, the same type of database can function as both the source and destination.

NOTE #2

Connections to cloud databases (e.g., Amazon RDS, Google Cloud, or Azure SQL) aren't explicitly specified in the user interface but use the same settings as traditional on-premises databases.

NOTE #3

Connections to source and target databases remain active until you close the DBConvert/DBSync application or reopen new connections.

Refer to our documentation for specific source/ destination configurations for different databases.

3

Configure database migration options

Specify the tables, fields, indices, and views you want to transfer to the SQL Server destination database by checking/unchecking the corresponding boxes.

Customize general database/ tables settings. Or configure specific table, field, index object individually when migrating data.

Explore our articles in the user's manual about Configuring database migration options for detailed information.

4

Detection of potential database migration issues

The database enforces certain relations on the data, and on the customization step, an intelligent error checker verifies all possible data integrity and referential integrity issues. It highlights any problems before migration starts.

By default, DBConvert attempts to automatically map the database types of the source Access database to the closest equivalent of the target SQL Server database types. However, you can manually change the data types for the entire database globally using the "Global mapping" or individually for each field.

Explore the Intelligent error checker for more information on errors and warnings.

5

Execution - The final stage of data migration

Initiate the conversion or synchronization process after configuring source and destination databases in the previous steps.

Click the "Commit" button to start conversion. Here, you can also monitor the conversion/synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or conversion jobs regularly.

Execution step of DBConvert products

Explore more about the options available during the execution stage.

DBConvert Software Features

DBConvert screenshot

Command line mode

Pass previously saved sessions as parameters to the Command-Line DBConvert Client. A session retains Access source and SQL Server target database connection settings with other specified options.

Example:

C:\Program Files\DBConvert\access2mssqlPro\access2mssqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler

Our applications include a built-in scheduler to run database conversion and sync jobs at specified times. Set the scheduled date and time to execute job sessions automatically.

Find more Information about the built-in scheduler.

DBConvert scheduler screenshot

System Requirements

Ensure your system meets these requirements for optimal performance

Supported OS

Requirements

  • Microsoft Visual C++ 2010 x86 Redistributable package
  • Access 2000 or higher. Both Access 32/64 versions are supported
  • Necessary privileges to write into database on the target SQL Server (this requirement is optional as there is an option to overcome the restrictions using dump file)

Additional Information

Explore related resources and key features

Related Links

Highlights