Articles
Assuring Data Integrity in DB2 - Part 1
Written by Craig Mullins Monday, 01 February 2010 00:00
DB2 provides mechanisms to automatically enforce and maintain the integrity of data as it is added to, and modified within, DB2 tables. The simplest form of data integrity enforcement available to DB2 is with data typing. By choosing the appropriate data types, DB2 will force columns to contain only the proper form of data (e.g., character, numeric, date). Of course, DB2 offers more sophisticated forms of ensuring data integrity, too. Features such as referential integrity, check constraints, triggers, validation routines, and edit procedures all can be used to ensure the integrity of DB2 data.
Assuring Data Integrity in DB2 - Part 2
Written by Craig Mullins Monday, 01 February 2010 00:00
In part 1 of this article, you learned some of the mechanisms that DB2 provides to automatically enforce and maintain the integrity of data as it is added to, and modified within, DB2 tables. Referential integrity, including RI referential constraints, referential sets, and referential integrity guidelines were discussed. Part 2 of this article discusses more of these mechanisms, highlighting check constraints and their guidelines, code constraints, and more.
Data Warehouse Performance Options
Written by Dave Beulke Wednesday, 27 January 2010 00:00
There are many options available to help you improve the performance of your data warehouse, and knowing all the different aspects of performance, issues, and considerations for building your data warehouse can be a tremendous task. DB2 offers many performance enhancements missing from other DBMSs that can make a huge difference. This article will highlight the performance advantages of DB2 and how to handle all the design issues, alternatives, and considerations experienced while building a large high-performance data warehouse.
Isolation level UR the beauty and the beast in one
Written by Klaas Brant Tuesday, 06 October 2009 01:00
DB2 for z/OS uses locking in order to guarantee that you will never get incorrect or invalid data. The locking mechanism will protect you both from logical and physical corrupt data. Part of the locking is the isolation level which can be set either at bind time or at each individual SQL statement. Other databases also support isolation levels; but there is not a standard for isolations. Different implementations use different names for the same thing. This can be confusing. Via the isolation level you instruct DB2 how deal with locking. Many people never really studied locking.
Read more: Isolation level UR the beauty and the beast in one