Kerri said:
Hello,
I am new to this. I am not sure to post here or sql so I am starting here
first. I am hoping someone can tell me on how to best handle a current
access db (2007) and import to lastest sql 2005. There is no current sql
database except to run Moss2K7. Are there any known issues or is it not a
good idea to import. Please help. The database is growing and I am
afraid that it will slow down performance of access. Infopath forms are
pulling data from access as well.
There's an upsizing wizard that should do the conversion for you.
On the other hand, upsizing because of a vague foreboding that "growing and
afraid it will slow access" is often a waste. Very often, too, if you only
take the data tables into SQL Server (or other server), the result is often
to _slow_ performance rather than improve it.
A well-designed, adequately-performing monolithic Access database with the
tables split into a separate Jet/ACCDB and put on a server machine in the
LAN with linked tables does not necessarily yield a well-designed,
adequately-performing multiuser Access database; neither a well-designed,
adequately-performing monolithic Access database nor a well-designed,
adequately-performing multiuser Access database with its tables,
relationships and data moved into SQL Server (or other server) necessarily
yields a well-designed, adequately-performing client-server database
application. The approaches to improving performance are different in each
of those environments.
How big is it? How much slowdown have you observed? What have you done to
improve performance? You'll find some excellent performance tips in various
Access resource websites, especially in MVP Tony Toews' site, and
former-MVP, now MSFT employee on the Access team, Jeff Conrad's. There's a
list of links to resource sites at
http://sp.ntpcug.org/accesssig/default.aspx -- not nearly all good
resources, but all in that list are, IMNSHO, good ones.
Larry Linson
Microsoft Office Access MVP
