Hi,
we are installing DB2 V7.1 on AIX 4.3.3 in a RS6000 with 2 processors & 1 GB
Ram.
This is for a very simple application that for now has only inserts &
selects, there are no updates or deletes.
The main table in this application has this "logical" design: (there are
other small tables)
CREATE TABLE acta (
actcod CHAR(9) NOT NULL constraint unique,
acttipo CHAR(1) NOT NULL,
actfmtimagen CHAR(3) NOT NULL,
cdnro INTEGER NOT NULL,
actimagen BLOB(512K) NOT NULL)
The application is programmed in Java (JSP, servlets) & run in WebSphere AS.
It just an online query to show actimagen (which are jpgs & tiffs) in the
browser, accesing by actcod which is unique.
We have to load about 3M rows initially & expect to grow at a rate of about
100000 rows/month on the first year.
I'm new to the environment & have lots of doubts on the physical design of
this table and the strategy for backup/recover.
We are going to use db2 load initially but don't know if we can do it after
that while there are people querying the table. Is that possible using
"dirty read"? Remember there are no updates.
Is it worth to log the rows? (I think it's not)
If I do not log, how should I backup & recover?
Will the table grow too large & should I "split" it on n tables (say
acta01,..,acta0n) to manage it more easyly?
Can anybody comment on this?
Any question you had & ideas will be wellcome
TIA
Horacio Villa
TTI S.A.
Buenos Aires - Argentina
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
