Although it may sound similar,but both of them have specific usage when it comes to the optimizer. This post we will try to see difference between the two.
As the name suggests FETCH FIRST 5 ROWS ONLY, it actually puts a limitation on the number of rows the query is returning.I am assuming here n=5. So, here user gets only 5 rows even though there can be 100 qualifying rows for that query.
OPTIMIZE FOR 5 ROWS will straight way influence the optimizer.It does not limit the number of rows SQL will return. So using this , we will get all the qualifying rows,may be incrementally.Intent here is to give priority to retrieve first few rows.Once optimizer understands this ,it will give preference to access plan that will minimize the response time.So,DB2 will send the rows in a single block. Consider the below scenario where this will come handy.
You have an online application where the screen can hold details of 5 customers at a time. Suppose you have the below query to fetch the customer details
Select Fname, Lname, Dept, Sal,Rollno
From Dept table
Order by Sal Desc;
We are assuming the index to be defined on Rollno. If a descending index also exists on SAL column, its likely to have low cluster ratio.
Without using the OPTIMIZE clause, DB2 will do a full table space scan and sort on sal column to fetch you the details.
Now on Adding 'ÓPTIMIZE FOR 5 ROWS' to the query, DB2 will use SAL index directly because it knows you need the details of 5 highest paid employees.
So, it displays 5 rows to the screen and depending on user input will process the next 5 or do something else.Here DB2 encourage matching index scan and would not prefer list or sequential prefetch. Access plan selected for 5 records may not be good for 100 rows.
Thus, this OPTIMIZE clause comes handy for queries where you can process incrementally.We can use it to get rows directly from table without going through any buffering operations like sorting.