SQL server backend and WANs

[BT]

Hello,

I wanted to use a SQL server or something else as a back end for my Access
database in order to improve performance over a WAN. Can anyone point be to
an online article or a good book on the subject.

I am learning as I go here, so I'll need something that starts at the
beginning.

thanks again
BT

 

[J. Clay]

In the past, I have been able to use and Access Data Project (ADP). I made
sure that all of my main forms only returned one record at a time by using
Stored Procedures with parameters and inputparameters on the forms. There
are a couple of books I would recommend. One being the Guru's guide to
transact SQL. (I think that's the title). I don't recall the author and I
am not in my office today. This book will help writing SQL Stored
procedures, triggers, etc. There are a couple of books on Access and SQL.
I believe that Mary Chipman's is the defacto standard.

HTH,
Jim

 

[Norman Yuan]

It is most likely rather more network capacity issue than database issue,
when you are talking "improve performance", unless the WAN connection is so
fast that you are sure it is the database that makes the "bottle neck".

 

[BT]

The problem is it is too slow for people from other offices trying to access
it. From reading other posts I know I will need to limit the about of records
that are returned to users, if I use SQL server. I am just not sure what goes
in to setting up a the SQL tables and how to connect to it. That's what I am
researching so I can make the proposal to those folks who control the $$$.

thanks for your advice
BT

 

[J. Clay]

If you have an MDB now that is split (Front end/Back end) you can start your
conversion by simply using the upsizing wizard to upsize the backend to SQL
Server. You then relink the tables in the Front End to the SQL Server
rather than the original back end MDB.

To get optimum performance, the biggest step is to rewrite the Front end to
pull a limited number of records (preferebly 1). I personally prefer using
an ADP, but there are some that will argue against this. It is purely your
preference and comfort in terms of development tools and abilities. I would
suggest you learn as much about SQL and the options with Access as possible.

HTH,
Jim