Access to SQL Server conversion and synchronization.

DBConvert & DBSync for Access and MSSQL is cross-database migration software for converting and synchronizing data between Microsoft Access (.MDB or .ACCDB) and SQL Server on-premises or in a cloud.

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.

MS Access vs SQL Server

Microsoft Access SQL Server
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. The SQL Server database usually performs much better than an Access database, especially with a large, terabyte-sized database.
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. By default, SQL Server allows a maximum of 32767 concurrent connections, the maximum number of users who can simultaneously log in to the SQL server instance. SQL Server processes queries much faster and efficiently by processing queries in parallel, using multiple native threads within a single process to handle user requests.
MS Access applications are NOT designed to be exposed to the Internet. There are some workarounds, such as Remote Desktop Connection, but these systems are always expensive to build and maintain. In most cases, it also shows poor performance. SQL Server can be easily configured for accessing over the Internet. Typically, the application interface connects to SQL Server databases over the Internet. Thus, employees, partners, and customers can exchange information and update it in real-time, wherever there is Internet access.
Overgrown Access databases can often crash and become corrupted. The built-in limitations of the MS Access applications itself, or sometimes the application's design quality, restrict its 24/7 operation. Let's say an operating system crash or power outage occurs. In this case, SQL Server can automatically restore the database to a consistent state in minutes and without the database administrator's intervention.

Migrate Access to SQL Server

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.

However, for large data storage volumes with many clients, it would be reasonable to consider migrating a database to cloud-based solutions.

Why use DBConvert SQL Migration tools?

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

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

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 is a 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 for Access and SQL Server is designed to synchronize data between Access and SQL Server databases.

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

Notes.

Note #1 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.

Note #2 Forms, reports, macros, and VBA modules are not converted.

Note #3 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.

Supported databases:
  • Microsoft Access x86/x64
  • Microsoft SQL Server
  • Access queries → MS SQL Server views
  • Azure Database for SQL Server
  • Amazon RDS
  • Amazon Aurora
  • Google Cloud
  • SQL Dump
 DBConvert for Access & MSSQL

Version: 6.1.6

Release Date: April 17, 2024

 DBSync for Access & MSSQL

Version: 4.1.8

Release Date: May 21, 2024

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 4.0.5

Release Date: May 16, 2024

Supported databases:

  • SQL Server
  • MySQL
  • MariaDB
  • Percona
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Interbase
  • Firebird
  • IBM DB2
  • MS Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Using Access to SQL Server conversion and synchronization 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.

The screenshot below summarizes the general features available in DBConvert software.

4. Detection of potential database migration issues. Errors and Warnings

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 migration/synchronization process.

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

Execution step of DBConvert products

Explore more about the options available during the execution stage

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 migration 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 screenshot

Supported OS:

Requirements

  • Microsoft Visual C++ 2008 x86 Redistributable package
  • 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)
  • Access 2000 or higher. Both Access 32/64 versions are supported

Highlights

Explore details regarding reverse migration.