|
 |
asp_databases thread: ASP and MS Access performance
Message #1 by gbrown@c... on Mon, 9 Sep 2002 18:42:48
|
|
Hi all
I am using Access for the backend to an ASP application.
I have two clients who have huge datasets 350-500mb MDB, when I query this
file it has been known to actually bring down the webserver. The query in
particular sums up to twelve child records and updates two fields on a
parent table.
I currently do not use Indexes with this system as I remember reading
somewhere that it makes no difference to the performance, which I find
strange.
Could anyone give the definitive answer to this, if I have reached the
limits of Access then I'd probably be better off spending the time working
out how to upsize to SQL.
Regards
Graham
Message #2 by Greg Griffiths <greg2@s...> on Tue, 10 Sep 2002 20:06:33 +0100
|
|
Regardless of any other suggestions I would certainly look for moving to
SQL Server or Oracle ASAP with that size of data.
At 18:42 09/09/02 +0000, you wrote:
>Hi all
>
>I am using Access for the backend to an ASP application.
>
>I have two clients who have huge datasets 350-500mb MDB, when I query this
>file it has been known to actually bring down the webserver. The query in
>particular sums up to twelve child records and updates two fields on a
>parent table.
>
>I currently do not use Indexes with this system as I remember reading
>somewhere that it makes no difference to the performance, which I find
>strange.
>
>Could anyone give the definitive answer to this, if I have reached the
>limits of Access then I'd probably be better off spending the time working
>out how to upsize to SQL.
>
>Regards
>Graham
>
|
|
 |