Sometimes we forget. It isn’t so much getting older (I hope) but more that we continue to get busier and busier. With the rush to pick up and handle the new tasks that are thrown our way we sometimes miss the basics. Application design that takes into account performance is one of those basics...
Most relational tuning experts agree that the majority of performance problems with applications that access DB2 are caused by poorly coded programs or improperly coded SQL. A great deal of time is spent on tuning your SQL but how much time are you spending tuning or conducting performance reviews o
What’s the main difference between single-row and multi-row inserts? Simply the performance. If you are inserting many rows in a loop via a single-row insert, you call DB2 for every single row, which means you spend some time for the communication with the DB2.
For the past 30 years, our focus as DB2 for z/OS database administrators has been on the support of COBOL programs with static queries that were relatively easy to control as they were identical throughout the business logic. Static SQL provided persisted access paths in the database s
This month’s third article is by John Maenpaa. John provides us with the overview of a real life project. The choice was between JSON, XML and traditional relation structure, in order to store complex forms. John talks about measurements and considerations. This article is a must read.