I have to agree that many of these features are in there and yet, it takes
a severe beating to get people to actually use them.
I argued for a long time that we should be doing journalling. Could only
get them to implement it on a limited table by table basis and only after
the horse got out of the barn.
- How can we find out who's been monkeying around with this data?
- I suspect this one batch EDI job has been hosing this data. How can I
- Crap. I forgot the where clause on my DELETE statement. How can I get
this data back?
Looking at receivers can tell you this information. And, in the case of
the errant delete statement, retrieve all the data right back.
Finally, when we implemented a H/A solution (Mimix), did we finally have
journalling on all data.
Date fields. My Lord! They are still using numeric dates on new tables.
Constraints. They still have to occasionally go through and delete the
duplicate records out of files. I can't even get them to use a primary
key constraint. Let alone check constraints or referential constraints.
Granted, it's not just DB2 on the System i where I see this. I once moved
a system from Access to DB2. Lots of corruption there also. No
Then again, the gent who set that up came from an AS/400 background.
This thread ...
Re: Which of the SYSIBM tables/views show the row count for, (continued)
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact