Continuous block fetch

When you use continuous block fetch to retrieve large, read-only result sets in a distributed environment, you can achieve better response time.

With continuous block fetch, fewer messages are transmitted from the requester to retrieve the entire result set. In addition, overlapped processing is performed at the requester and the server.

However, continuous block fetch might use more networking resources than limited block fetch because multiple sockets are opened concurrently. When networking resources are critical, use limited block fetch to run applications.

The requester can use both forms of blocking at the same time and with different servers.

Two types of continuous block fetch are available:

• Package-based continuous block fetch, which is initiated by the DBPROTOCOL(DRDACBF) bind option. This is the preferred type of continuous block fetch.
• SQL-based continuous block fetch, which is initiated by the OPTIMIZE for n ROWS SQL clause.