Migrating ODBC Connections from Access to SQL Database
Hi All,
I don't have much experience using SQL directly; however, I've created an Access Database that I'm considering migrating up to SQL. In my database, I have ODBC connections to our IBM system that are required. What I'm trying to figure out is can I continue to have those connections if I were to migrate it. Also, does anyone know of any resources where I can get a better understanding on the migration process overall?
Thank you.
I don't have much experience using SQL directly; however, I've created an Access Database that I'm considering migrating up to SQL. In my database, I have ODBC connections to our IBM system that are required. What I'm trying to figure out is can I continue to have those connections if I were to migrate it. Also, does anyone know of any resources where I can get a better understanding on the migration process overall?
Thank you.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Makes sense. I'll begin exploring this option.
Do you recommend any specific version of SQL?
Do you recommend any specific version of SQL?
>Do you recommend any specific version of SQL?
The most current version your employer can afford.
Try to weasel in some developer training into the conversation too.
The most current version your employer can afford.
Try to weasel in some developer training into the conversation too.
ASKER
Sounds good. Thanks.
I'll see if any of the Access people have things to add as well.
I'll see if any of the Access people have things to add as well.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
(no points please)
I agree with the others that your Access front-end would be fine using tables from both SQL Server and your IBM system. There's a reason it's called "Access".
To make your Access FE work correctly and perform well with SQL Server, you will need to make some changes to it. I've written a PowerPoint presentation on this. It's called "Best of Both Worlds" at our free J Street Downloads Page:
http://www.JStreetTech.com/downloads
Cheers,
Armen Stein
I agree with the others that your Access front-end would be fine using tables from both SQL Server and your IBM system. There's a reason it's called "Access".
To make your Access FE work correctly and perform well with SQL Server, you will need to make some changes to it. I've written a PowerPoint presentation on this. It's called "Best of Both Worlds" at our free J Street Downloads Page:
http://www.JStreetTech.com/downloads
Cheers,
Armen Stein
ASKER
Great solutions.
ASKER
Do you think I would have any performance issues leaving the local tables in the SQL Server?