using Access db for website - thoughts?

[Bobby Edward]

I am creating an ASP.NET website that might have 50 concurrent users using
it at 1 time (minimal data.) Will Access be ok for this or will the
concurrent users accessing data pages blow up the site? Thanks...

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

RE: using Access db for website - thoughts?

if you cannot install SQL Server or SQLEXPRESS ( the free version of SQL
SERVER 2005), then you might try SQLite, which is a lot more performant than
MS Access - even though it too is file-based.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: htp://petesbloggerama .blogspot.com
Short Urls & more: http://ittyurl.net


"Bobby Edward" wrote:

I am creating an ASP.NET website that might have 50 concurrent users using
it at 1 time (minimal data.) Will Access be ok for this or will the
concurrent users accessing data pages blow up the site? Thanks...
>
>
>

[Phil H]

Re: using Access db for website - thoughts?

On 21 Feb, 18:53, "Bobby Edward" <t...@test.comw rote:

I am creating an ASP.NET website that might have 50 concurrent users using
it at 1 time (minimal data.)  Will Access be ok for this or will the
concurrent users accessing data pages blow up the site?  Thanks...

There is an alternative if the data is only being read and not written
to (except perhaps occasionally by an administrator), namely putting
the data into XML files. The number of concurrent users doesn't matter
then and it saves having to bother with SQL server.

If that's not the case, is there any reason for not using SQL Server
2005 Express? It's free and is not restricted in respect of concurrent
users so long as it is running on the same server as the web site
(i.e. local connection only).