Migration to SQL-Server

Can anybody help me with preparing a migration from  Jet to SQL-Server 2005.

* I want to use the upsizing wizard.
* I use MS Jet replication now.
* All tables already have unique keys with GUID fields.

When using a SQL-Backend:
* What problems will arise - what are common approches to handle these.
* Will DAO work? What about necessary OpenRecordset parameters.
* and, and, and.

I suppose there must be some manual out there in the Internet. I hope that these type of material will prevent me to post tons of questions here when running into these problems.
Thanks
Chris
chriswiesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tbsgadiCommented:
Hi

Check out http://support.microsoft.com/?kbid=241743
"Access 2000 Upsizing Tools" White Paper Available in Download Center

Gary
0
IT-SchubertzCommented:
Hi,

There are a bunch of resources about migrating from Access to SQL Server. A good page to start on is http://www.microsoft.com/sql/solutions/ssm/access/accessmigration.mspx.

Specific information about using the Upsizing Wizard is found here: http://www.microsoft.com/technet/prodtechnol/sql/2000/Deploy/accessmigration.mspx as well as in the Access help.
Even though those ressources talk about SQL 2000, the Upsizing Wizard is the same and all the information in the paper still appliy to SQL 2005.

One special point for SQL 2005 Express: you will need to enable TCP/IP connection in order for Access to talk to SQL Server. This is off by default in the Expr.  Edition. You can configure this using the SQL Configuration Manager ( http://msdn2.microsoft.com/en-us/library/ms181035.aspx )
.
Some more information if Access & SQL Server are not at the same machine: http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Nontheless, I would recommend using SSIS (former DTS) features to import the data into Yukon

hth

Andy
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.