| | |
|
|
|
Converting back end data to SQL database tables |
|---|
| message from Denise on 7 May 2004 |
Is this something that a novice SQL user can do? I heard
that SQL will help to stabilize a multi-user database that
is being strained.
|
| Tony Toews replied to Denise on 07 May 2004 |
It can be a lot of work.
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
Tony
|
| Tony Toews replied to Denise on 07 May 2004 |
Define strained. What's happening that's giving you concerns? How
many users? 1) Have you split the MDB into a FE/BE? 2) Are you
having corruptions? 3) Are you having performance problems?
1) You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.
See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp.htm for more info. See
the Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.
2) For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm
3) visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm
Tony
|
| RobFMS replied to Denise on 7 May 2004 |
Denise
The real question to ask is, is it REALLY necessary to push the data to a
SQL Server. There are many issues involved when you want to take this next
step.
I would like to offer you to tour FMS's upsize site. There are several
whitepapers that discuss the move from Access to SQL Server. Hopefully with
this information, you can really decide if its necessary to move up or if
you just need to have some maintenance done on the Access application.
http://www.fmsinc.com/fmsupsize/
Let me know if you have any questions.
|
|
Archived message: Converting back end data to SQL database tables (Microsoft Access Database)
