I want to start developing a new site for myself that uses ASP and a 

backend database. I figure that the users will need to read heavily from 

the database and write fairly often to it. At the start there will not be 

many users but I would hope it would grow pretty fast. What type of 

database would you recommend using for scalability and that kind of wear? 

Any good web resources pertaining to the recommended DB would be great 

too. Right now I have really only used Access extensively but know that it 

is not very scalable at all. Thanks for the help. You are all truly 

amazing.

Hi Rick,



My understanding is that for larger applications, you should use SQL

Server.  I have never had any problems using Access though, but I don't

know what the breaking point would be (as far as too many users, etc.).

Pete





> -----Original Message-----

> From: Rick Brose [mailto:brose@u...]

> Sent: Wednesday, April 25, 2001 5:42 PM

> To: ASP Databases

> Subject: [asp_databases] Which database to use?

> 

> 

> I want to start developing a new site for myself that uses ASP and a 

> backend database. I figure that the users will need to read 

> heavily from 

> the database and write fairly often to it. At the start there 

> will not be 

> many users but I would hope it would grow pretty fast. What type of 

> database would you recommend using for scalability and that 

> kind of wear? 

> Any good web resources pertaining to the recommended DB would 

> be great 

> too. Right now I have really only used Access extensively but 

> know that it 

> is not very scalable at all. Thanks for the help. You are all truly 

> amazing.

> ---

> SoftArtisans helps developers build robust, scalable Web applications!

> Excel Web reports, charts: 

> http://www.softartisans.com/excelwriter.html

> File uploads: http://www.softartisans.com/saf.html

> Transactional file management: http://www.softartisans.com/saf1.html

> Scalability: http://www.softartisans.com/saxsession.html

> ASPstudio value pack: http://www.softartisans.com/aspstudiosuite.html



> PeterF@S...


> $subst('Email.Unsub')

> 

> 

Rick-



Here is a good explanation of the 2 different db packages:



Microsoft Access is a good standalone and easy to use database. Features

like autonumbering and cascade update are both supported under Access. You

can push an Access database up to 100 MB in size as long as minimal

concurrent connections are pulling and appending the records; however, once

you exceed 10 or more concurrent database connections, performance will

deteriorate significantly. While Microsoft states that an Access database

will support 30 to 40 concurrent connections, the HostPro shared Web service

environment cannot support this.



Microsoft SQL Server is a much more scalable solution than Microsoft Access.

While the size of the database is a consideration, the primary difference

between Microsoft Access and SQL Server is the number of concurrent sessions

supported by the database. Unlike Access, SQL Server supports up to 30,000

concurrent connections. Additionally, SQL Server does not require periodic

scaling or compacting of your database, a necessary step to preserve data in

Microsoft Access.





Matt





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

From: Peter Foti (PeterF) [mailto:PeterF@S...]

Sent: Wednesday, April 25, 2001 1:28 PM

To: ASP Databases

Subject: [asp_databases] RE: Which database to use?





Hi Rick,



My understanding is that for larger applications, you should use SQL

Server.  I have never had any problems using Access though, but I don't

know what the breaking point would be (as far as too many users, etc.).

Pete

Start with the Microsoft Data Engine... it is a 5-connection version of 

SQL Server... when you're ready to deploy the site, you can use SQL 

Server and not have to change any code..



Tomm



> -----Original Message-----

> From: Rick Brose [mailto:brose@u...]

> Sent: Wednesday, April 25, 2001 5:42 PM

> To: ASP Databases

> Subject: [asp_databases] Which database to use?

>

>

> I want to start developing a new site for myself that uses ASP and a

> backend database. I figure that the users will need to read heavily 

from

> the database and write fairly often to it. At the start there will not 

be

> many users but I would hope it would grow pretty fast. What type of

> database would you recommend using for scalability and that kind of 

wear?

> Any good web resources pertaining to the recommended DB would be great 



> too. Right now I have really only used Access extensively but

> know that it

> is not very scalable at all. Thanks for the help. You are all truly

> amazing.

In my experience... Access bogs down around 15 users when used for web 

sites....



Tomm



> -----Original Message-----

> From: Peter Foti (PeterF) [mailto:PeterF@S...]

> Sent: Wednesday, April 25, 2001 1:28 PM

> To: ASP Databases

> Subject: [asp_databases] RE: Which database to use?

>

>

> Hi Rick,

>

> My understanding is that for larger applications, you should use SQL

> Server.  I have never had any problems using Access though, but I 

don't

> know what the breaking point would be (as far as too many users, 

etc.).

> Pete

>

>

> > -----Original Message-----

> > From: Rick Brose [mailto:brose@u...]

> > Sent: Wednesday, April 25, 2001 5:42 PM

> > To: ASP Databases

> > Subject: [asp_databases] Which database to use?

> >

> >

> > I want to start developing a new site for myself that uses ASP and a 



> > backend database. I figure that the users will need to read

> > heavily from

> > the database and write fairly often to it. At the start there

> > will not be

> > many users but I would hope it would grow pretty fast. What type of

> > database would you recommend using for scalability and that

> > kind of wear?

> > Any good web resources pertaining to the recommended DB would

> > be great

> > too. Right now I have really only used Access extensively but

> > know that it

> > is not very scalable at all. Thanks for the help. You are all truly

> > amazing.

    If its for yourself, try MSDE (its free and comes with office... in fact you

might be able to download it or do what my friend did and order it on CD for

free).  Its basically a smaller version of SQL Server.  Then if you need to

scale up to SQL Server you really don't have to do much work.



- Chuck



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

From: "Rick Brose" <brose@u...>

To: "ASP Databases" <asp_databases@p...>

Sent: Wednesday, April 25, 2001 5:42 PM

Subject: [asp_databases] Which database to use?





> I want to start developing a new site for myself that uses ASP and a

> backend database. I figure that the users will need to read heavily from

> the database and write fairly often to it. At the start there will not be

> many users but I would hope it would grow pretty fast. What type of

> database would you recommend using for scalability and that kind of wear?

> Any good web resources pertaining to the recommended DB would be great

> too. Right now I have really only used Access extensively but know that it

> is not very scalable at all. Thanks for the help. You are all truly

> amazing.

The advantage of using SQL is you can link in live to your database and 

make changes. You can also use DTS to upload tables & objects into your 

database.



Using acess if you make changes at your end you have to upload the whole 

database replacing the live one which means the sites down for the length 

of the upload.