David Fitzjarrell

The advent of JSON (JavaScript Object Notation) has changed application programming, and, because of this, database vendors are adapting their products to

Transactions are the lifeblood of a relational database and Oracle is no exception. The key to this concept is the ability to replay those transactions

For every timeless adage there is at least one mistaken thought that can become 'truth' simply by virtue of being repeated. Oracle is no exception to this

Oracle has provided very useful tools and views to aid the DBA in database management> This includes a number of offerings dealing with the subject of

Automatic Memory Management (AMM) has been available since Oracle version 11, and it does a respectable job of managing the SGA and PGA. When it's

In-lists can be interesting constructs as far as Oracle is concerned. They allow users to return results for a large number of values with the restriction

There are occasions when two or more data sets need to be combined to produce the desired results, and a join is not possible (no common columns, no

Disaster recovery should be on the mind of every Oracle DBA, even though the goal is to never need it. Nonetheless, many enterprises run regular disaster

NULL values can be a performance issue as, absent an index of some sort, searching for them involves a full table scan. For small tables (less than 10,000

Occasionally a join using primary key columns in a query can be eliminated because of the data involved. If Oracle determines that all of the 'required'

Oracle DBAs should know how Oracle behaves and should also be able to address issues without the aid of a flashy graphical user interface (or GUI).

iOracle version 12 introduced the hybrid histogram as a performance improvement -- such histograms are based on 'rules' set forth in version 12.1. Those