Link to home
Start Free TrialLog in
Avatar of J.R. Sitman
J.R. SitmanFlag for United States of America

asked on

Need to convert Access database to SQL

We have an Access database that I want converted to SQL.  The reason is it is growing large.  We are the Society for the Prevention of Cruelty to Animals, (Non profit) amd can't afford to pay someone to do it.  I'm looking for anyone who might Volunteer to do it for us.  Also I heard rumor that there was a program that could automatically convert Access to SQL
Avatar of Ephraim Wangoya
Ephraim Wangoya
Flag of United States of America image

You can easily do this in SQL Management Studio

First create a database in SMSS

The right click on the newly created database, select Tasks->Import Data

You will get a wizard that will guide you through importing the Access dta into SQL Server

Basically you will need to select the datasource, in this MS Access, then enter the file name

Next you select the destination, which will be the database you just created, then select the tables you want transfered

it finish and you have your sql server tables created for you
Avatar of J.R. Sitman

ASKER

Sounds way to simple.  However, I'll try it and post later.
I made a copy of the current backend and when I go through the wizard I got an error so I did it again and chose "test connection" and got the same error.  See attached.
sqlconvert.png
>>Sounds way to simple. <<
You are right the conversion is simple. The fun starts later:
1. Syntax is different.
2. Data types that do not convert or are converted to "lowest common denominator" data types.
3. Lousy performance, because the app is written for MS Access not MS SQL Server.

Sorry to be the harbinger of bad news.  But it is best to be prepared, rather than frustrated and disappointed.
What version of Access are you running? It may be simpler to export all tables to SQL Server from Access. It's wizard driven as well.

However, per acperkins, the fun really begins after you get the data transferred. Some thoughts/opinions:

1) Using linked tables, you may only need to make minor modifications to any existing Access code.
2) Performance need not be 'lousy'. With qualified guidance you should experience performance that 's more than acceptable (but it'll never be optimal with an Access front end).
3) There's no real long term downside to migrating your data out of Access to SQL Server. It'll be time well spent.
ASKER CERTIFIED SOLUTION
Avatar of Scott McDaniel (EE MVE )
Scott McDaniel (EE MVE )
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for the updates.  I figured it was too good to be true.  

Anyway the error comes when I'm doing the import from the Access backend.  I rebooted the server last night and this morning when noone is connected, I tried again.  Same error.
Have you tried with the SSMA, linked in my earlier answer? That tends to give better results, at least for me.

SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
How do I remove the mdw from the backend?
I removed the security.  Then used the migration wizard.  Lots of errors.  So it seems obvious I won't be able to this on my own.  Any volunteers?  See attached errors.
op3.png
op2.png
op1.png
What version of Access is this database in?
Also what version is the front end in, because the backend wont be a problem?
2003, but we use it with 2007.  It is still an MDB
Thanks for all the help.  I used your information to do this with the assistance of a friend