Convert Access to SQL Server.

DBConvert/ DBSync for Access and Microsoft SQL Server are powerful cross database migration tools for upsizing and synchronization of Access x86/x64 data to MS SQL Server.

Generally the number concurrent users for an Access database is limited to maximum of 10-20 users. Access does not provide the level of security and reliability that SQL Server does. Besides, Microsoft said, that the MS Jet Database Engine that is used in MS Access, has entered a state of functional deprecation. They recommend using MS SQL Server Express or MS SQL Server Compact Editions instead for new database applications as a backend.

DBConvert for Access and MSSQL performs database conversion from Access 32/64 versions to Microsoft SQL Server/ Windows Azure SQL Databases and inversely. Other migration combinations are supported as well. The tool provides direct conversion but when you need to workaround firewalls MS SQL Dump files may be generated.

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

DBSync for Access and MSSQL is a powerful sync tool designed for two-way synchronization between Access and Microsoft SQL Server databases. Sync of data from MS Access to SQL Azure and vice versa is possible as well. It is also appropriate for database replication between two MS SQL Server databases. DBSync for Access and SQL helps to keep your Access, MS SQL, Azure SQL databases fresh and up-to-date satisfying all possible syncing needs.

Read more information about Types of Synchronization.

Remember, if you have restricted direct access to your MS SQL database, MS SQL Dump files may be generated.

Automate the process using our built-in scheduler and our powerful command-line mode.

It takes just 6 minutes to convert 1 million records from MS Access x64 to MS SQL Server.

 DBConvert for Access & MSSQL

Migration directions:

  • Access x86/x64 → MS SQL Server, MS SQL Dump
  • MS SQL Server → Access 32/64
  • Access queries → MS SQL Server views
  • Access 32/64 ↔ SQL Azure
  • Access x86/x64 ↔ Amazon RDS

Version: 6.1.1

Release Date: June 23, 2020

 DBSync for Access & MSSQL

Sync directions:

  • Access ↔ MS SQL Server
  • Access ↔ SQL Azure
  • MS SQL Server ↔ SQL Azure
  • Access ↔ Amazon RDS

Version: 4.1.3

Release Date: Jan. 15, 2020

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

DBConvert Studio

 Version: 1.8

Release Date: Aug. 4, 2020

Supported databases:

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

Related Links

Supported OS:

Using Access to SQL Server conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to Access source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to Access source database from DBConvert

2. Connect to SQL Server destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to SQL Server target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • Access to SQL Server
  • SQL Server to Access
  • Access to Access
  • SQL Server to SQL Server

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the SQL Server destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from Access to SQL Server.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

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

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source Access database to the closest equivalent of the target SQL Server database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from Access to SQL Server

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ 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

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps 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, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

Requirements

  • 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)
  • Microsoft Visual C++ 2008 x86 Redistributable package