The number of claim requests is shown in Figure 2-25. As expected, the number of claim  requests per transaction dropped. During this measurement, a 25% reduction in the number  of claim requests was observed for the Db2 12 measurement compared to the Db2 11  measurement.  Db2 12 introduces a fast path mechanism for SELECT INTO SQL statements that reference  an equal predicate with a unique index in the WHERE clause. This kind of SELECT statement  always has a result set of one or zero rows. Such statements are categorized as singleton  selects with unique index access.  Db2 12 provides a shorter code path to perform matching key index scan for this type of  SELECT statement. By using this specialized code path, Db2 can avoid having to use the  general runtime environment and the overhead that is associated with its ability to handle all  variations of SELECT INTO statements. All SELECT INTO statements with unique index access benefit from this optimization in Db2  12 at function level V12R1M100 and beyond. However, a REBIND is required to enable this  “fast path” for SELECT INTO statements. The use of APREUSE(ERROR) is sufficient to allow  Db2 to use the enhancement when applicable. Chapter 2. Scalability enhancements and subsystem performance  75 2.8.3 SELECT INTO optimization  Figure 2-25 Claim requests reduction for the Brokerage workload run in Db2 12 versus run in Db2 11