Hi, 



I am designing a database to hold approximately 3MB of data. What I am 

intending to do is use this database as a backend system to hold the 

information that will be displayed on the web. None of this information 

will be editable, just readonly. What I want to know is whether Access 

will stand the load if many of people are accessing the data to be 

viewed on the web. I know that access cannot handle more than 5 concurrent 

users, but that is if they are updating the information at the same time. 

This database's content will only be viewed.



I would also like to know what will be the effects of the database if 

many people are viewing the information held in it at the same time.



As far as ASP is concerned, my code will is written in the best possible 

way, where I have adopted the 3-tier apporach and I only open quieries 

when I need to and close them straight away.



Your help will be most appreciated. Would also apprecitate links to any 

sites holding any relevant information.





Thanks

Access is a low traffic database. Consider other options such as SQL if you

anticipate heavy usage...



-----Original Message-----

From: Kalwinder Dohil [mailto:kdohil@t...]

Sent: Wednesday, January 23, 2002 8:48 AM

To: Access ASP

Subject: [access_asp] How reliable and scalable is Access?????





Hi, 



I am designing a database to hold approximately 3MB of data. What I am 

intending to do is use this database as a backend system to hold the 

information that will be displayed on the web. None of this information 

will be editable, just readonly. What I want to know is whether Access 

will stand the load if many of people are accessing the data to be 

viewed on the web. I know that access cannot handle more than 5 concurrent 

users, but that is if they are updating the information at the same time. 

This database's content will only be viewed.



I would also like to know what will be the effects of the database if 

many people are viewing the information held in it at the same time.



As far as ASP is concerned, my code will is written in the best possible 

way, where I have adopted the 3-tier apporach and I only open quieries 

when I need to and close them straight away.



Your help will be most appreciated. Would also apprecitate links to any 

sites holding any relevant information.





Thanks

I am sure someone will beat it but I have provided Access apps (user

front end and storage back end) over 50 meg in size, with both reading

and writing.



According to Access help you can up to 255 concurrent sessions per

database. - I think the scaled down version of SQL Server (MSDE) on

supports 5 users if I remember rightly. 



Of course there are ways round limitations and a whole host of other

things to take into account.



Regards



Paul 



-----Original Message-----

From: Kalwinder Dohil [mailto:kdohil@t...] 

Sent: 23 January 2002 13:48

To: Access ASP

Subject: [access_asp] How reliable and scalable is Access?????





Hi, 



I am designing a database to hold approximately 3MB of data. What I am 

intending to do is use this database as a backend system to hold the 

information that will be displayed on the web. None of this information 

will be editable, just readonly. What I want to know is whether Access 

will stand the load if many of people are accessing the data to be 

viewed on the web. I know that access cannot handle more than 5

concurrent 

users, but that is if they are updating the information at the same

time. 

This database's content will only be viewed.



I would also like to know what will be the effects of the database if 

many people are viewing the information held in it at the same time.



As far as ASP is concerned, my code will is written in the best possible



way, where I have adopted the 3-tier apporach and I only open quieries 

when I need to and close them straight away.



Your help will be most appreciated. Would also apprecitate links to any 

sites holding any relevant information.





Thanks




$subst('Email.Unsub').

I'd recommend MySQL for this kind of load and job. It's what the P2P site

uses. Massive speed and scalability and you can even admin it using a

freeware application for Win32 called MySQL Frontend

(http://anse.de/mysqlfront/) which is similar to the admin interface of SQL

Server. Very easy to work with.



Dan





> Hi, 

> 

> I am designing a database to hold approximately 3MB of data. What I am 

> intending to do is use this database as a backend system to hold the 

> information that will be displayed on the web. None of this information 

> will be editable, just readonly. What I want to know is whether Access 

> will stand the load if many of people are accessing the data to be 

> viewed on the web. I know that access cannot handle more than 5 concurrent 

> users, but that is if they are updating the information at the same time. 

> This database's content will only be viewed.

> 

> I would also like to know what will be the effects of the database if 

> many people are viewing the information held in it at the same time.

> 

> As far as ASP is concerned, my code will is written in the best possible 

> way, where I have adopted the 3-tier apporach and I only open quieries 

> when I need to and close them straight away.

> 

> Your help will be most appreciated. Would also apprecitate links to any 

> sites holding any relevant information.

> 

> 

> Thanks

In a internet or intranet I have found it very reliable and extremly 

scalable because it ports to SQL Server within minutes.



For the use you describe a Microsoft Access database will work fine. If 

this database is only for read-only use via ASP you can use this solution 

indefinitely. I have created several sites that are much larger and they 

are extremly reliable; however, if you ever anticipate using a larger 

database (20mb or larger)it is better to upsize it to SQL Server using the 

upsizing wizard that is part of Microsoft Access, change your connection 

string and you should be up and rolling.





Note: With ASP.NET and the new SQL Managed Provider you get very efficient 

communication with SQL Server 7 or SQL Server2K.



Jonathan Conley

Senior Software Engineer

www.revinteractive.com



> Hi, 

> 

> I am designing a database to hold approximately 3MB of data. What I am 

> intending to do is use this database as a backend system to hold the 

> information that will be displayed on the web. None of this information 

> will be editable, just readonly. What I want to know is whether Access 

> will stand the load if many of people are accessing the data to be 

> viewed on the web. I know that access cannot handle more than 5 

concurrent 

> users, but that is if they are updating the information at the same 

time. 

> This database's content will only be viewed.

> 

> I would also like to know what will be the effects of the database if 

> many people are viewing the information held in it at the same time.

> 

> As far as ASP is concerned, my code will is written in the best possible 

> way, where I have adopted the 3-tier apporach and I only open quieries 

> when I need to and close them straight away.

> 

> Your help will be most appreciated. Would also apprecitate links to any 

> sites holding any relevant information.

> 

> 

> Thanks

Let's clear some nomenclature here. Some of us seem to be talking about

"Access" (the Jet-driven desktop database) when what they're describing is

actually MSDE. Kalwinder asks "How reliable and scalable is Access?" The

answer is that ACCESS is notoriously unreliable and unscalable and is being

scrapped by its manufacturers in favour of MSDE.



MSDE, on the other hand, is a reliable and moderately scalable DB that

offers considerable compatability with SQL Server and can support up to 16

different databases on the same server. However the use Kalwinder describes

is multiple users making simultaneous queries via the web interface, for

which MSDE is restricted by design. MSDE will tie up if more than 5 of

users make requests at any one time - so it's useful for small intranet

sites (where I've used it) or web sites that do not have a large audience

and never anticipate having one.



However, like I say, the 32-bit Windows version of MySQL seems to be

entirely what Kalwinder is looking for. MySQL is ideal for sites that only

do read or read & append work on their database. P2P runs on MySQL, and it

is at least as fast as SQL Server would be at the same job.



Dan



> In a internet or intranet I have found it very reliable and extremly 

> scalable because it ports to SQL Server within minutes.

> 

> For the use you describe a Microsoft Access database will work fine. If 

> this database is only for read-only use via ASP you can use this solution 

> indefinitely. I have created several sites that are much larger and they 

> are extremly reliable; however, if you ever anticipate using a larger 

> database (20mb or larger)it is better to upsize it to SQL Server using the 

> upsizing wizard that is part of Microsoft Access, change your connection 

> string and you should be up and rolling.

> 

> 

> Note: With ASP.NET and the new SQL Managed Provider you get very efficient 

> communication with SQL Server 7 or SQL Server2K.

> 

> Jonathan Conley

> Senior Software Engineer

> www.revinteractive.com

> 

> > Hi, 

> > 

> > I am designing a database to hold approximately 3MB of data. What I am 

> > intending to do is use this database as a backend system to hold the 

> > information that will be displayed on the web. None of this information 

> > will be editable, just readonly. What I want to know is whether Access 

> > will stand the load if many of people are accessing the data to be 

> > viewed on the web. I know that access cannot handle more than 5 

> concurrent 

> > users, but that is if they are updating the information at the same 

> time. 

> > This database's content will only be viewed.

> > 

> > I would also like to know what will be the effects of the database if 

> > many people are viewing the information held in it at the same time.

> > 

> > As far as ASP is concerned, my code will is written in the best possible 

> > way, where I have adopted the 3-tier apporach and I only open quieries 

> > when I need to and close them straight away.

> > 

> > Your help will be most appreciated. Would also apprecitate links to any 

> > sites holding any relevant information.

> > 

> > 

> > Thanks