Migrating to SQL server

G

Guest

Does anyone has practical experience on migrating Access application (built on Jet) to SQL server database? If so, appreciate to share the effort spent. Do I have to change all codes? Do I have to write connection or just relink the database as spilt manager does?
 
T

Tony Toews

Peter said:
Does anyone has practical experience on migrating Access application (built on Jet) to SQL server database? If so, appreciate to share the effort spent. Do I have to change all codes? Do I have to write connection or just relink the database as spilt manager does?

Do a search at the Knowledge Base at support.microsoft.com using the
keywords "upsizing" to review the various white papers on upsizing
Access to SQL Server as well as to ensure you have any updates
required.

Also see my Random Thoughts on SQL Server Upsizing from Microsoft
Access Tips page at
http://www.granite.ab.ca/access/sqlserverupsizing.htm

You can start off easy with your conversion and debottleneck by
creating views and stored procedures as you see what's slow.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
G

Guest

Thanks. Does it mean that I need to re-write part of the application (eg codes, forms etc) ? I read some books, if correct me if I am wrong, that Access 2003 FE is compatible with SQL database.
If I ignore the performance issue, can I just run the FE with SQL server database with tables re-link? Please help urgently as I have to decide whether SQL is our decision for upsizing.
 
T

Tony Toews

Peter said:
Thanks. Does it mean that I need to re-write part of the application (eg codes, forms etc) ? I read some books, if correct me if I am wrong, that Access 2003 FE is compatible with SQL database.
If I ignore the performance issue, can I just run the FE with SQL server database with tables re-link? Please help urgently as I have to decide whether SQL is our decision for upsizing.

Correct. So long as your queries don't have spaces in the names and
aren't stacked (one calling the next and so on) you can relink the
tables to SQL Server and go.

FWIW this will be a lot less painful than going to, say, Oracle,
simply because they are from the same vendor.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
T

Tony Toews

Tony Toews said:
Correct. So long as your queries don't have spaces in the names and
aren't stacked (one calling the next and so on) you can relink the
tables to SQL Server and go.

Just to clarify this. Both conditions must be true before you might
have problems. (Or maybe it's fixed in A2003.). That is the query
names have spaces in them *and* and they are stacked.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
G

Guest

Thanks Tony. You are very helpful and saved me a lot of time. I believe the company has decision on our direction
Thanks again.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top