Server Databases

[Guest]

Hi,

I'm in my first job and have been working on the access databases here for a
month. My boss has limited DB knowledge and said he wants change to a server
database. My first thoughts were SQL server, but he wants to stick with
access.
What he wants is to improve the data retrieval speed and ultimately use ASP
applications to access the database.
Please can someone give me on advice on firstly whether Access is the
correct option, if it is where I can find info on using it as a server
database or if we should start looking at SQL server.

Thanks a lot,
Chris

 

[Baz]

The default Access database engine (often referred to as Jet) is not, and
cannot be made into, a server database engine. An Access application can be
split such that the file containing the user interface objects (forms,
reports and so on, the "front end") resides on the workstation, and the file
containing the data tables (the "back end") resides on a file server, and
indeed there are usually compelling reasons to do this. However, this does
*not* make it a client/server application: all the processing continues to
be done on the workstation, the server does nothing but act as a shared
location for the back end.

So, if he wants a server database engine, he can't stick with Access (Jet).
SQL Server is the most obvious alternative. But, why does he want to do
this? Do you currently have, or do you anticipate, performance problems?
Do you need the greater security and resilience that comes with a server
database engine? If the answer to these questions is "no", then it's a
classic case of "if it ain't broke don't fix it".

There is no reason why an Access (Jet) database cannot be used in an ASP
application so long as the anticipated number of concurrent users is small.
For a busy public website it would be madness.

 

[Guest]

Hi,

Thanks for the response. We are currently experiencing performance problems.
One of the probelms is concurrent users accessing the same databse and
causing havoc when updating the DB while the other person is still sorking on
it. I've read that access can be used as a front end to a SQL server
database, is this a wise course to follow? He also wants to ultimately use
ASP to allow clients to view certain parts of the database. Any advice is
greatly appreciated.

Thanks,
Chris

 

[Baz]

Sorking?!

Access (Jet) has limitations, but nonetheless a well-designed and tuned
Access application can perform extemely well for smallish user numbers. How
many users do you have? Have you asked for help here with your specific
performance problems?

Having said that, if you have lots of users then Access (Jet) is probably
the wrong choice. Access can indeed be used as a front-end to a SQL Server
database, and this is often a very wise course to follow.

As I said before, your Access (Jet) database can be used by an ASP
application, but once again it depends on your user base: lots of users,
forget it, use SQL Server.

Sorry, I am unable to define "lots of users", because this is largely
dependent on the nature and design of your application and the profile of
your users' activity.