Design for backup in mind Was: Backup strategy

Ok let's say you're current with hardware and software. Let's also say
you have the capability to learn and adapt. So you've read about such
things as "Identity columns" "sequences", etc. Your have the freedom to
design from scratch. Now, you want to write your application with some
stability in mind. You just read some emails between Rob and Jeff and say
this saving of journal receivers on a periodic basis bears some merit.
Now, let's say your concern is, I have a new order number. I could use an
identity column. However how would this receiver strategy handle that?
So, I run a test.

CREATE TABLE ROB/DESIGN
(ORDERNBR INT NOT NULL AS IDENTITY,
CUSTNBR INT NOT NULL)
SAVOBJ OBJ(DESIGN) LIB(ROB) DEV(*SAVF) SAVF(ROB/ROB)
INSERT INTO ROB/DESIGN (CUSTNBR) VALUES(1)
INSERT INTO ROB/DESIGN (CUSTNBR) VALUES(1)
INSERT INTO ROB/DESIGN (CUSTNBR) VALUES(2)
INSERT INTO ROB/DESIGN (CUSTNBR) VALUES(3)
select * from rob/design
+....1....+....2....+....
ORDERNBR CUSTNBR
1 1
2 1
3 2
4 3
**** End of data ******
RSTOBJ OBJ(DESIGN) SAVLIB(ROB) DEV(*SAVF) OBJTYPE(*FILE) SAVF(ROB/ROB)
APYJRNCHG JRN(ROB/QSQJRN) FILE((ROB/DESIGN)) RCVRNG(*CURRENT)
4 entries applied to 1 objects.
INSERT INTO ROB/DESIGN (CUSTNBR) VALUES(27)
select * from rob/design
+....1....+....2....+....
ORDERNBR CUSTNBR
1 1
2 1
3 2
4 3
1 27
**** End of data ******

Dang nab it!!!! Just what I was concerned about!!! The current value for
the identity column is not journaled!
Time for another DCR.

I suppose you could use a "sequence" and journal the data area.

Rob Berendt