Can I use access for big database (cca 10-30 MB, cca 10-30k lines in
database). It will be asp.net 2.0 aplication and very fast server. Mostly
simple transactions (like SELECT * From Books Where Name like 'SomeName%').

Can it be problem if I have 10 000 unique visitors per day? I see that many
big sites have access database. Is it ok, ir it is big risk?

Igor wrote:
> Can I use access for big database (cca 10-30 MB, cca 10-30k lines in
> database). It will be asp.net 2.0 aplication and very fast server. Mostly
> simple transactions (like SELECT * From Books Where Name like 'SomeName%').
>
> Can it be problem if I have 10 000 unique visitors per day? I see that many
> big sites have access database. Is it ok, ir it is big risk?

Assuming that:
- you have index on Name column
- the MDB is on a local disk
- the disk is not heavily used by something else
- the unique visitors only make one query (or only a few)
- the load is reasonable good distributed over time
then it should not be a problem.

30 MB can easily be cached in disk/file cache.

10000/day is only 7/minute over 24 hours or 21/minute over
8 hours and that is not heavy.

Arne

You might want to cache items that are very often run (but seldom change)
queries.

There is a Cache object in the System.Web namespace.

You can also find an object called "WeakReference" which is a way to cache
items, but to release them if there is a memory drain.

I wouldn't start with Access. I'd start with MSDE (2000) or Sql Express
(2005).

But you might be able to pull it off.



"Igor" <(E-Mail Removed)> wrote in message
news:emr8st$t2b$(E-Mail Removed)...
> Can I use access for big database (cca 10-30 MB, cca 10-30k lines in
> database). It will be asp.net 2.0 aplication and very fast server. Mostly
> simple transactions (like SELECT * From Books Where Name like
'SomeName%').
>
> Can it be problem if I have 10 000 unique visitors per day? I see that
many
> big sites have access database. Is it ok, ir it is big risk?
>
>

Igor,

It is the same as the others wrote, however probably easier to manage.

You can set a dataset shared in your program. Because all your users share
the same application is that for all your users. It has to be a dataset that
from the userside will never be changed otherwise you should never create a
shared dataset in an AspNet appliction.

Don't forget to make an extra page to set the dataset to nothing, otherwise
you can never change it.

Cor

"Igor" <(E-Mail Removed)> schreef in bericht
news:emr8st$t2b$(E-Mail Removed)...
> Can I use access for big database (cca 10-30 MB, cca 10-30k lines in
> database). It will be asp.net 2.0 aplication and very fast server. Mostly
> simple transactions (like SELECT * From Books Where Name like
> 'SomeName%').
>
> Can it be problem if I have 10 000 unique visitors per day? I see that
> many big sites have access database. Is it ok, ir it is big risk?
>

use SQL Express, it is free and durable

"Igor" <(E-Mail Removed)> wrote in message
news:emr8st$t2b$(E-Mail Removed)...
> Can I use access for big database (cca 10-30 MB, cca 10-30k lines in
> database). It will be asp.net 2.0 aplication and very fast server. Mostly
> simple transactions (like SELECT * From Books Where Name like
> 'SomeName%').
>
> Can it be problem if I have 10 000 unique visitors per day? I see that
> many big sites have access database. Is it ok, ir it is big risk?
>

> use SQL Express, it is free and durable
>
Hi Igor,

Are you from the Netherlands?

Cor



> "Igor" <(E-Mail Removed)> wrote in message
> news:emr8st$t2b$(E-Mail Removed)...
>> Can I use access for big database (cca 10-30 MB, cca 10-30k lines in
>> database). It will be asp.net 2.0 aplication and very fast server. Mostly
>> simple transactions (like SELECT * From Books Where Name like
>> 'SomeName%').
>>
>> Can it be problem if I have 10 000 unique visitors per day? I see that
>> many big sites have access database. Is it ok, ir it is big risk?
>>
>
>

> Hi Igor,
>
> Are you from the Netherlands?

No, I am from Croatia!

> Assuming that:
> - you have index on Name column
What index?

> - the MDB is on a local disk
It is on web hosting account like www.webhost4life.com. It is on fast server
(i hope that it is true).

> - the disk is not heavily used by something else
It is shared hosting, but good hosting.

> - the unique visitors only make one query (or only a few)
One or few queries in one page load.

> - the load is reasonable good distributed over time
Distribution... hmm. It is for tourist agency. Visitors mostly come at
summer. I don't know how many often at different hours.

> 30 MB can easily be cached in disk/file cache.

Can I cashe this if it is not on my server. It is on shared hosting named
webhost4life.com or something simmilar (profesional hosting).

> 10000/day is only 7/minute over 24 hours or 21/minute over
> 8 hours and that is not heavy.

What if 100 or 300 visitors come at the same second and every of them
request 2-3 select queries?

I thought that you was Dutch, because there was asked about speed and you
are answering about the cost.

:-)

Cor

"Igor" <(E-Mail Removed)> schreef in bericht
news:emtigs$v3j$(E-Mail Removed)...
>> Hi Igor,
>>
>> Are you from the Netherlands?
>
> No, I am from Croatia!
>

1. Go into Table view of the MDB containing the actual data.
2. Open the table in design mode.
3. Go to the bottom of the screen under the 'General' tab.
4. Find the Indexed property and set it to 'Yes" either with or without
duplicates, depending on your data.
(this may vary a little bit depending on your version of Access)

Brooks

Igor wrote:
> > Assuming that:
> > - you have index on Name column
> What index?