Microsoft Access

Microsoft Access


  • The Customer ‘Access’ and 2SQL Stories – ‘On-a-Page’

    Typical Customer profile, Business & Technology Drivers, and 2SQL solution outcomes ‘On-a-Single-Page’.

    Download Document
  • Business & Technical Drivers Behind Access to SQL Server Conversions

    What’s driving the need for businesses to convert their Access databases to the Microsoft SQL Server Platform?

    Download Document
  • Moving Access databases to a Multi-tenant Environment

    Consolidate your many Access databases in to a single Multi-tenant database structure.

    Download Document
  • 2SQL Flyer

    Access 2013 is based on the SQL Server platform, acknowledging the fact that older versions of Access have both functional and commercial limitations. Companies whose Access footprint is large or which contain complex and mission- critical applications could face a daunting conversion effort.

    Download Document
  • MSO Inspector Flyer

    MSO Inspector™  analyses network drives across an enterprise, auditing , logging and reporting detailed information about the Microsoft Access or Excel application population.

    Download Document
  • CU2 Global – first to automate the conversion and migration of Microsoft Access to SQL Azure

    CU2 Global releases 2SQL Azure – a world first automation program for converting and migrating Microsoft Access to SQL Azure, delivering in excess of a 95% automation capability

  • Discovering & Reporting on Microsoft Access Database Populations

    The MSO Inspector is used to scope the size and complexity of a corporate wide Microsoft Access to SQL Server conversion program. It searches network drives gathering detailed metadata on all Access databases discovered. This data can then be used to determine which Access databases are candidates for conversion, and which can be either archived or left as is.  The MSO Inspector can also be used to gather detailed metadata on Microsoft Excel files.

  • Case Study – Luca Technologies

    A Colorado biotech company developing long-term, biotechnology-driven solutions to the rising US dependence on foreign energy sources. Luca Technologies had outgrown the capabilities of its Microsoft Access database, requiring a database platform with scalable client-server architecture, robust security, and one which would facilitate its obligations under data compliance regulations.

    Download Document
  • 2SQL Conversion Project Services Guide

    This document highlights the 2SQL Conversion Categories where manual services may apply after 2SQL  has completed its automated migration and conversion work.

    Download Document
  • 2SQL Functionality Overview

    High level overview of the 2SQL program components and the functions that they fulfil during an MS Access to SQL Server conversion and migration program.

    Download Document
  • 2SQL Conversion Methodology Paper

    Information for senior managers regarding 2SQL’s practical, fast, cost-saving approach to Microsoft Access to SQL Server Conversion.

    Download Document
  • South Australia’s Top 20 Innovation Awards – February 2010

    “Database Miracle earns Converts” heads the article covering ConvertU2 Technologies 7th placement in the South Australian Top 20 Innovation Awards of February 2010.

    Download Document
  • 2SQL White Paper – Converting Access to SQL Server

    This White Paper explores commercial and technical drivers for converting Access to SQL Server; limitations of incomplete hybrid conversions; issues which must be addressed for a complete conversion; and how 2SQL assists the conversion to SQL Server in much less time and expense than current alternative methods.

    Download Document
  • 2SQL MSO Inspector User Guide

    This guide details the steps for using the 2SQL MSO Inspector for scanning of Access Databases or Excel Files, reporting of metadata and properties that assist in Business Intelligence initiatives and in measuring overall migration and conversion complexity.

    Download Document
  • 2SQL Technical Reference Guide

    The 2SQL Technical Reference Guide describes each of the “conversion issues” that 2SQL identifies and automatically addresses.

    Download Document
  • 2SQL Toolkit

    This document explains the features and functionality of the 2SQL Toolkit – software utilities and documented processes which support the process of arriving at a fully and completely converted Microsoft Access database to SQL Server.

    Download Document
  • 2SQL User Guide

    The User Guide fully describes all of the steps for using 2SQL from setup and installation; to scanning a database for conversion issues; to processing the database to apply its automated conversions; and finally to the Manual Cleanup phase to complete the conversion and migration process.

    Download Document
  • 2SQL Detective Quick-Start Guide

    This is a Quick-Start guide for users wishing to run the 2SQL Detective to identify the conversion issues associated with converting a MS Access database/application to SQL.

    Download Document
  • How to Deploy a 2SQL Conversion Project

    Synchronizing  production and development databases for final deployment can be a complex and time consuming process. 2SQL delivers this capability in a simple turnkey manner.

    Download Document
  • 2SQL MSO Inspector Technical Reference Guide

    Analyse the company’s Microsoft Access and Excel application population across its network drives. Obtain comprehensive metadata details of the Access/Excel footprint. Determine candidate Access applications/databases for conversion to SQL Server

    Download Document
  • 2SQL Version 5.4.0 Release Notes

    Release Notes for 2SQL Version 5.4.0

    Download Document
  • Preparing & Transferring Files to the CU2 Global FTP Site

    How to prepare and upload Access Databases to the CU2 Global secured FTP site for Analysis.

    Download Document
  • 2SQL Management of Microsoft Access Workgroup Security

    Handling Microsoft Access Workgroup Security on Access databases to be converted to SQL Server by 2SQL

    Download Document
  • 2SQL Set-up in High Security Environments

    Highly Secured Environments often require complete application isolation to protect corporate data and applications.

    Download Document
  • CU2 Global Releases Version 5.5.7 of 2SQL

    Release Notes for 2SQL Version 5.5.7

    Download Document
  • Case Study – Asian Food Logistics

    Food Logistics company uses 2SQL to open the door to international web data collaboration.

    Download Document
  • Case Study – MyBudget

    MyBudget – an Adelaide based personal finance and debt management company – underpins business growth through integration to Microsoft SQL Server.

    Download Document
  • Case Study – Department of the Chief Minister – NT Government

    The Department of the Chief Minister, the central strategic coordinating arm of the Northern Territory Government, needed to migrate their underperforming legacy Travel database application to “future proof” the functionality in a low cost and highly accurate manner.

    Download Document
  • 2SQL Live Demonstration Video

    Live demonstration of 2SQL automatically converting a Microsoft Access database/application to SQL Server.

There are three main reasons to consider investing in a conversion project:

  1. Data compliance.  Largely arising from Sarbanes-Oxley or similar rulings, good corporate governance requires that enterprise mission-critical data must reside on secure, controlled, centrally managed servers.
  2. Scalability and performance.  Once an Access database reaches a certain size or complexity, performance becomes significantly compromised, especially when communicating to data over a network.   In contrast, SQL Server is very efficient, highly scalable and supports unlimited users.  “Processing” is moved from the Access client to the SQL back end.
  3. SQL reporting benefits.  SQL Server is the gateway to the development of Web-enabled applications and makes available a variety of Business Intelligence reporting tools to facilitate the refreshing of your User Interface.

The reasons to migrate to SQL Server are very compelling, but the pathway from one environment to the other requires very careful preparation and planning, and should not be attempted without the appropriate steps being followed. 

Developing a new front end can be very expensive and time consuming. Access is a relatively simple and flexible tool for creating databases, forms, and reports and you have already done much of the hard work. 2SQL makes the conversion possible and affordable. You can keep the familiar front end application that your people already know so there is no new training needed.

Creating the schema and migrating the data is easy. Converting an Access database to an SQL back-end is HARD. Conversions require an in-depth knowledge base of both Access and SQL Server language, and often the conversion of thousands of deep technical issues which are not only very hard to locate, they ALL have to be found and fixed. Incomplete conversions can cause a lot of problems. For example, even the simplest of Access Databases can contain one Crosstab query. If a Crosstab Query is left alone to stay as a client side process, it will either malfunction or cause performance to grind to a halt.

Re-engineering is even harder than converting and migrating, unless you can remove 75% or more of the existing functionality. If your database is functional in Microsoft Access, it is better to consider any kind of re-engineering after the migration process, not before.

The less you convert, the more client-side processing is required. Only databases with small amounts of data and SQL Statements that are not complex will work without compromise for a client-side solution.

If your database does not have Tables with thousands of rows, and your Queries are not complex, there is a possibility that the Wizard or SSMA can deliver an uncompromised solution. The Microsoft Access Upsizing Wizard and SSMA (SQL Server Migration Assistant for Access) will only take you from 5% to 20% of the way to a Server side processing based solution leaving 80% to 95% left to be converted manually.

Please visit our 2SQL Workings (Comparison of 2SQL vs MS Wizard & SSMA) page for more information.

2SQL will convert 80% to 95% of the database AUTOMATICALLY. It removes virtually all of the programming associated with manually converting Access data and applications to SQL Server.

  1. It is a fully self-contained product which will migrate Table Schema and Data. 

  2. The 2SQL conversion process is fast and accurate, is completely self-auditing, and generates an XML report listing every change made and every issue unable to be changed.

  3. The software converts Access Tables, Queries, Forms, Reports and Code Modules, and achieves up to 95% conversion with no programming errors to chase and correct.

  4. Leverages your investment in Access – the change to SQL Server is completely transparent to the end user. There is no re-training required.

  5. 2SQL will allow your developers to work quickly reducing the time of a conversion project by up to 90% and it will significantly reduce the overall cost.


For complex databases, the saving in time is massive. Twelve month migration projects (excluding testing) can be reduced down to between four and six weeks. Three month projects can be conquered in two to three weeks. 2SQL is continually evolving and has reached the stage where it can now detect and repair 95% or more of all conversion issues, leaving very little mostly administrative ‘cleanup’ work to done to complete the project

The larger and more complex the conversion, the greater will be the time (and cost) savings when compared with manual conversion. Please click here to take you to the CU2 Uni Library page to access the 2SQL Conversion Project Services Guide document that describes the cleanup process in some detail.

2SQL is easy to operate and understand, but the person using it should be a skilled Access/SQL developer so they can understand what it is that 2SQL is doing and be able to interpret and understand the reports so they can do the manual cleanup to quickly complete the project.

The amount of cleanup will depend on the complexity of the application. Some DAO to ADO conversion issues may remain, some compilation errors, some views and stored procedures may not have upsized to SQL Server. 2SQL provides very comprehensive reports of all actions in the conversion process. It provides a detailed list of every issue repaired and a report which highlights the issues that still require manual intervention, saving many hours of having to find remaining issues by trial and error.

Please click here to take you to the Library page to access the 2SQL Conversion Project Services Guide document that describes the cleanup process in some detail.

Our pricing model is based on the complexity of the Applications, not the size of the databases. This ensures that you only pay for the work that 2SQL does, irrespective of whether or not your conversion project is simple or complex

When we (or you) scan your application with the 2SQL Detective it determines the number of Conversion Issues that exist.  Some conversion issues are easy to fix and others are very complex.  We assign a “rating” factor of 1 to 8 to the different types of conversion categories to determine characteristics such as conversion hours saved utilizing 2SQL.

Once we know the number of Conversion Issues we will be able to provide you with a quotation for 2SQL and for the cleanup work, should you wish us to complete the conversion for you.  Using this approach we can calculate accurate costs for each database conversion project and you only pay for the work 2SQL does.  Simple projects will cost less and complex projects will be priced higher, while the cost and time for each will be cut drastically from doing the work manually.

For the very large conversion projects, we offer an alternative pricing model. This is the annual Enterprise Licence option where an organization is able to perform as much conversion work as it is capable of during a 12 month period. There is no limit to either the number of databases/applications or the number of corresponding conversion issues, that can be converted/consumed during the 12 month period

A project with hundreds of Access databases to convert manually can involve a number of programmers with the Access/SQL Server skillset and span several elapsed years. This is the scenario where 2SQL shines because the licence fee will only be a fraction of the manual cost, and the elapsed time can also shrink to a few months in lieu of the years to do the conversions manually.

The “Detective” function within 2SQL scans the database for conversion issues. You can register on the web site and download 2SQL and run the Detective on your database to get a sense of its complexity. Share the Conversion Issues report with us and we can provide a quote for your conversion project

When you have acquired the licence to resolve Conversion Issues you will be supplied with a new software license key which will let the Genie out of the bottle. It is the Genie side of 2SQL that will process your database and apply all of the conversions. It may take an hour or two for the Genie to apply all of the hundreds or thousands of code changes. At the completion of the process you will have reports detailing what was fixed and what issues remain to be fixed manually.

Yes. We can take on the entire project for you. Send us an empty copy of your database (front end and tables) and we will scan it to determine the number of Conversion Issues needed. We will inspect the reports and the database to determine the extent of the clean up and provide you a quote for the project

CU2 Global will be pleased to quote to deliver a completed turnkey solution, or you may choose to outsource only the cleanup work to us. Similarly, you may also license 2SQL and then outsource the clean up to a local service provider who you know and who has the Access and SQL skills to complete the project for you. You may choose whichever approach suits you best.

Microsoft has decided to end support for the ADP model in favour of ODBC Linked Tables. ODBC has been given a new life as a connectivity protocol and server-side based Linked Table solutions are in fact easier to implement and have fewer complications than ADP.

Providing the processing of SQL Statements is server based, performance increases can be at least 10 fold, but where performance does not have a significant improvement, applying Table indexes in the appropriate Table columns usually solves the problem.

Yes. The record source and row source properties of Forms and Reports may be modified during the conversion process but on the whole this is transparent to the end user. Minor changes to the GUI are rarely required.

There is no restriction to future enhancements, but a Developer must focus on server-based processing as opposed to client-based processing when implementing new features. This means that aside from changes to the GUI, most of the new legacy code should reside in SQL Server with hooks from the Access front end, e.g. ADO, to do the processing.

Every single issue that 2SQL rectifies is stored in an XML file and an Access database. Users can write their own reports from these two data storage protocols.

Our 2SQL Conversion Project Services Guide document, (CU2 Library), has a repair status indicator for each issue. This ranges from complete, to partial, to failure. In addition, this document explains what to look for manually. These are issues that 2SQL does not, or cannot repair.

This is a part of our services delivery when we are contracted to deliver either a full turnkey solution, or just the post-conversion cleanup work. It is not a part of our standard 2SQL Licence Fee and will be the subject of a Statement of Work quotation to suit each specific circumstance.

© All Rights Reserved CU2 Global