A Warehouse Application
A data collection specialist
describes how he uses HSQLDB to power an ordering and warehouse
I've deployed HSQLDB (initially version 1.8, now already 2.0) as a
server for warehouse applications for multiple customers.
installations usually service about 30 JDBC connections, of which,
during daytime, well over 25 may be actively processing data, and
least one (belonging to a server-based data exchange and archiving
application) does so constantly and with notable intensity.
volumes have ranged as high as 250,000 articles and 50,000 saldos.
of workload is generated by sales orders, of which about 50,000
kept in the active database ,together with about 500,000
order and picking batch rows. About 500 orders tend to be
daily. For our typical customers, this amounts to about 3 months'
of data kept in a database schema for everyday work, while an
schema hosts more historical information.
consist of a Linux-based database server, a number of portable
collection terminals operating over wireless LAN, running either
Windows CE, Windows Mobile or compact distributions of Linux,
less of fixed warehouse workstations, and a couple of workstations
using a management interface built on OpenOffice Base.
preferred HSQLDB since its JDBC driver worked well with the
(which is a good choice for Windows CE), and since it was already
internal database engine of OpenOffice (though upgrading to a
which bypasses OpenOffice required solving some puzzles). Ability
address some tables with schema-relative names and others with
names, and define views pointing from one schema to another proved
handy for implementing an archive database. Ability to write
Java functions, put them in the server classpath and address them
SQL was quite helpful on occasions. Overall, HSQLDB has proven a
choice for me.