Adam wrote:

> You mention two tables and seem to toggle between them. Is there a
> reason for doing it this way? If it is just an information lookup,
> then you could put the data into a new database (on a different
> machine) and then put the database in and change the alias.

This was an interesting proposition, which I will take into
consideration. One problem is that the DB also contains a few other
tables that are not toggled like this - just a single one of each. If I
were to use two DB:s I'd have to put these tables in a separate third
DB, and they'd have to be filled using cross-DB techniques, i.e. a
select/insert loop in my application. But I think that process could be
put in a background low-prio worker thread, so it might be ok. Might
also allow me to switch off forced writes on the two DB:s with the
toggled tables, because that info is not critical - if it's lost I just
run the update process again.

> Also, the hardware is relatively modest for something that is meant to
> be both a database server, web server as well as handling data pumping.

Yes, but this is a low-traffic site. I think we've topped about 15-20
concurrent user sessions. Nevertheless, they need to be able to run some
SQL queries with decent response times.

Kjell
--
--------------------------------------
Kjell Rilbe
Adressmarknaden AM AB
E-post: kjell.rilbe@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64