Re: Cross: Access speed
SQL Express is not well suited to shared hosting environments, especially
if your provider is using IIS 6.0 or above and has assigned every site it's
own application pool, which is the most common scenario.
SQL Express is good, however it is a bit of a memory hog, it uses a fair
chunk of memory, at least 80-100Megs. If the server is hosting hundreds of
sites using SQL Express you can see how this might become a problem pretty
quickly.
Alternatively if your application is in a shared pool then SQL Express is
probably OK; however you will have all the security and reliability
problems that come with that sort of environment.
If you really believe your site is going to get that much traffic, make your
life easy, just develop for SQL Server.
If you use Access you're probably going to have to get into some threading
stufff, code a DAL with a mutex to stop multiple threads simultaneously
trying to write to your Access file, reads could be less of a problem but I
wouldn't bet my life on it's reliability.
In any case with Access, response times are going to be an issue under load,
and in many cases it's going to crash and require continuous
recycling/rebooting of your server or application pool (depending on the
setup).
Michael
"Rotsey" <malcolm_smith@ RemoveThis.optu snet.com.auwrot e in message
news:u820NkYKHH A.1248@TK2MSFTN GP02.phx.gbl...
SQL Express is not well suited to shared hosting environments, especially
if your provider is using IIS 6.0 or above and has assigned every site it's
own application pool, which is the most common scenario.
SQL Express is good, however it is a bit of a memory hog, it uses a fair
chunk of memory, at least 80-100Megs. If the server is hosting hundreds of
sites using SQL Express you can see how this might become a problem pretty
quickly.
Alternatively if your application is in a shared pool then SQL Express is
probably OK; however you will have all the security and reliability
problems that come with that sort of environment.
If you really believe your site is going to get that much traffic, make your
life easy, just develop for SQL Server.
If you use Access you're probably going to have to get into some threading
stufff, code a DAL with a mutex to stop multiple threads simultaneously
trying to write to your Access file, reads could be less of a problem but I
wouldn't bet my life on it's reliability.
In any case with Access, response times are going to be an issue under load,
and in many cases it's going to crash and require continuous
recycling/rebooting of your server or application pool (depending on the
setup).
Michael
"Rotsey" <malcolm_smith@ RemoveThis.optu snet.com.auwrot e in message
news:u820NkYKHH A.1248@TK2MSFTN GP02.phx.gbl...
use SQL Express, it is free and durable
>
"Igor" <igor@nesalji.h rwrote in message
news:emr8st$t2b $1@sunce.iskon. hr...
>
>
>
"Igor" <igor@nesalji.h rwrote in message
news:emr8st$t2b $1@sunce.iskon. hr...
>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?
>>
>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?
>>
>
Comment