ASP/Access DB

I have a small company creating a small site. Until it
gets big, they
switch to an MSSQL database hosted on a full-t1 site, and
all that jazz
they've got lowly ol' me working it into an Access
database.

I'm logging all the code with a logging function I
created. The log
function writes a row to the database each time I call the
function with
something like, "User logged into the web site".

I came to the stark realization that each time a user
loads my page they hit
the database with an SQL query at least 40 times. That
seems like a lot.
It seems unecessary given the simplicity of the site.

I realized a lot of my data is static. So I thought, "why
do i need to hit
the database and pull this data constantly if it will
rarely change?"

What methods are people using to mitigate database hits?
Can a simple array
be stored into a global ASP variable that all the sessions
could access?
XML (but I don't really know it well yet)?

I'm looking for advice, thanks!

Atrax
Mon Jul 21 22:17:32 CDT 2003

> Can a simple array
> be stored into a global ASP variable that all the sessions
> could access?

no, but you can but a FreeThreadedDomDocument in there....




________________________________________
Atrax. MVP, IIS
http://rtfm.atrax.co.uk/

newsflash : Atrax.Richedit 1.0 now released.
http://rtfm.atrax.co.uk/infinitemonkeys/components/Atrax.RichEdit/

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Dave
Tue Jul 22 11:32:52 CDT 2003

I'm developing a site in a similar manner. I plan on using the Server's Task
Scheduler to initiate an Access database at midnight. Once open, Access will
run a macro to recreate a .htm file. The Task Scheduler will also close the
program after it has run for 5 minutes which is more than enough time to
create the updated .htm file.
Perhaps this idea will suite your needs too.

Dave


"Kashi McGilloway" <ask@me.for.it> wrote in message
news:043f01c34fe6$fdbfe570$a501280a@phx.gbl...
> I have a small company creating a small site. Until it
> gets big, they
> switch to an MSSQL database hosted on a full-t1 site, and
> all that jazz
> they've got lowly ol' me working it into an Access
> database.
>
> I'm logging all the code with a logging function I
> created. The log
> function writes a row to the database each time I call the
> function with
> something like, "User logged into the web site".
>
> I came to the stark realization that each time a user
> loads my page they hit
> the database with an SQL query at least 40 times. That
> seems like a lot.
> It seems unecessary given the simplicity of the site.
>
> I realized a lot of my data is static. So I thought, "why
> do i need to hit
> the database and pull this data constantly if it will
> rarely change?"
>
> What methods are people using to mitigate database hits?
> Can a simple array
> be stored into a global ASP variable that all the sessions
> could access?
> XML (but I don't really know it well yet)?
>
> I'm looking for advice, thanks!
>
>