[dba-Tech] database

Good suggestion

-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Saturday, January 26, 2013 3:10 PM
To: Discussion of Hardware and Software issues
Subject: Re: [dba-Tech] database

Jim,

Given that it's a POS system, then I would want to distinguish its two
primary functions: data-entry and data-accumulation (for want of a better
term). That in turn suggests a pair of identical-looking databases, one
dedicated to each purpose. Given that performance is the priority in the
data-entry aspect of a POS system, there's almost no reason to lug about a
lot of data. Transactions could be recorded into an almost-empty database
(save the lookup tables, which obviously would not be empty, but also would
seldom be updated). Then some sort of replication process would copy
yesterday's sales to the larger database, against which almost all reports
would be executed. This could even be a three-stage process, a db for
Today's Sales, This Month's Sales, and everything older.

A.
_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com