Data Architecture is not only related to the mere constellation of technical components that should work together. A data architecture should also reply to the needs of an end user and eventually establish an information architecture that is not only fit for use, but also fit for purpose.
Database services in the cloud are gaining increasing popularity for development, test, and production systems. One of the key technical challenges for cloud database adoption is fast and secure movement of large data volumes into the cloud.
One of the more difficult parts of developing a data architecture for a new project is choosing which technologies to use. You'll have application developers that have their opinions, management with a different view, and legacy technology already in place.
In Part 1, I talked about some of the first steps that a developer should go through when it comes to tuning queries. In this article, I will go through the initial steps in evaluating a SQL query using the Db2 explain output.
