Will using an Access Database for my ASP.NET limit the number of people who can be on my website at a time?

I read that Access will only allow a few concurrent users. So, If I use an Access(mdb) database for a product catalog on my ASP.NET website, will there be a limit to how many people can look at the catalog at one time?Will using an Access Database for my ASP.NET limit the number of people who can be on my website at a time?
Access databases (you're really talking about MS Jet) has a limitation of 255 users, but it just gets unbelievably slow with less than that. Microsoft themselves don't recommend more than 20 concurrent users. You could try the free SQL Server Express, or Oracle 10g Express.





You will hit first the XP Pro, 2000/NT Workstation limitation of 10 concurrent connections. ASP in Vista has the same limitation, but instead of returning an error it will queue requests.Will using an Access Database for my ASP.NET limit the number of people who can be on my website at a time?
For a product catalog, I would think you are just looking up product, description, price, etc. So you can query all the data into a local dataset/array/datatable at page load and close the connection to Access.





If you had multiple people actually ordering things simultaneously you might have the limits issue you describe, but for a product catalog I would think it's not an issue.





hope that helps
Yes it will. Access is not a relational Database Management System. It is a Jet engine.





If you expect a higher number of concurrent users to access your website reading and writing data to your data tier, you should consider using SQL Server instead.
I agree with plez on this one. As long as you close the connection after retrieving data for some portion of the catalog, Access will probably be sufficient.





搂
yes another great answer smutty





Yes it will. Access is not a relational Database Management System. It is a Jet engine.





If you expect a higher number of concurrent users to access your website reading and writing data to your data tier, you should consider using SQL Server instead.
MS Access is a poor choice for an online database as a large number of simultaneous users could cause errors or even corrupt the DB and it doesn't have robust security or query performance. Much more popular databases for developing online apps are MySQL or the free (express) versions of Oracle, DB2 and SQL Server.





If you cannot get those databases installed onto your web server than MS Access will be good enough for lower traffic volumes.

horses for loan

skin care