Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: Access 2003 to SQL Server  (Read 2336 times)

0 Members and 1 Guest are viewing this topic.

snehadulur

    Topic Starter


    Rookie

    Access 2003 to SQL Server
    « on: July 02, 2009, 09:22:56 AM »
    Our company database has been running for 15 years now, there is a separate front and back end both running on Access, we are looking to convert it from Access to SQL server, how do we go about it, what are the procedure/rules to be followed?

    DaveLembke



      Sage
    • Thanked: 662
    • Certifications: List
    • Computer: Specs
    • Experience: Expert
    • OS: Windows 10
    Re: Access 2003 to SQL Server
    « Reply #1 on: July 02, 2009, 03:00:39 PM »
    Are you looking for a basic conversion or do you also have VBA scripts to consider that may break?

    We converted from Access 97 to SQL and had tons of troubles and ended up having to revert back to Access 97 and have an outside consultant perform the migration which cost about $15k in the end. I believe the consultant had to export all the tables to SQL and then recreate the linking rules etc for the data, and properly construct sections that prior were band-aided with VBA scripts that used to control Access 97 with Visual Basic 6 control hooks.

    This consultant was able to do this on alternate hardware so that the structure was able to be manually recreated with linked tables etc, and then when tests came up as good to go, he then just had to re-export access 97 tables back into SQL and the additional data up to that point was rolling into the new structure and we were able to go live with it that night and had an almost seamless transition the following day with only a few minor changes required that were missed that were not major. Users were amazed at how more quickly reports were generated under the SQL Database vs Access 97, big performance increase with querys and reporting.

    Rules/Procedures: Be sure to backup the databases before making any changes to them to protect the integrity and also have the databases ready to run if you run into troubles like we did, so the company can function the next day if you pull an all nighter like we did in which we ended up having to pull the plug at 3am and revert back to the way that it worked under Access 97 and get outside help with a professional DB Engineer who was fluent in Access and SQL migration 3 weeks later.