Connecting to Db2 remotely means the use of a client. Sometimes that client is installed software and other times it is as thin as a JDBC driver. In any event, a client talking to a Db2 server will invoke one or more bound packages on the server side. Let's discuss!
This is the first of a series of articles focused on setting up an Apple computer as a development environment for Db2 databases. The plan is to get the environment set up first, then some tools, and finally programming. The first step is installing Db2 using Docker.
In this article, we will learn about the legacy ways for applications to connect to Db2 for z/OS, and how this has changed and what new options we have depending on the nature of our applications.
This is part 2 in the series that focuses on improving performance in Db2 Warehouse databases. The first part gave some background and discussed some basic concepts relevant to query optimization in the context of the Db2 column engine.
Part 2 : Identifying Costly Operations + Improving Joins
Since the beginning, I/O has been one of the main determining factors for overall performance. I/O can easily surpass all other considerations, particularly if an SQL statement asks for a very large result or a missing index causes the scan of a very large table.