Sometimes, a change in the way Db2 for z/OS manages its resources is introduced, and the change “flies under the radar” (i.e, it escapes the notice of most Db2 users) because it is relatively small in terms of scope and impact and is not widely highlighted in the product documentation, and it delivers the intended benefit (e.g., enhances CPU efficiency for data access) and no one thinks about it — BUT, it may have a consequence that pops up in a surprising way, causing, initially, some …read more
Related Articles
Explaining InnoDB Explicit Locking Mechanisms
Introduction Locking mechanisms are critical to keep the database consistent (a fact that is not well understood by some developers). However, unnecessary locks can have a negative impact on system pe...
Oracle SQL Execution in a Parallel Server Environment
Introduction Execution of a SQL statement in an Oracle Parallel Server environment is slightly different then in a single instance environment. In an OPS environment additional instructions are execut...
A first look at Amazon Aurora with PostgreSQL compatibility – Benefits...
In this eight-part article series, we have had a good look at Amazon AWS and its Relational Database Service (Amazon RDS), in particular Amazon’s own Aurora database with PostgreSQL compatibility. In ...
