When using Data Studio browsing data in DB2 tables or query results, the default is to display only the first 500 lines:
How to display all the rows or specify the number of rows to display it? In the "Preferences - SQL developer> - -> Data Management> SQL results view options" settings:
The default number of rows to display SQL query result set to 500. Before custom settings to explain "the maximum row count" and "Max display row count" of these two parameters.
Maximum row count: the number of rows in the result set to fetch. Namely: the need to access memory in the result set number of rows. (CPU memory access)
The maximum display line count: the number of rows fetched to be displayed. Namely: For those rows have been fetched, the number of rows to be displayed in the corresponding Data Studio window. Cache line does not appear in the file.
If both are set to 0, indicating that all rows in the result set to fetch and display all the rows.
If the specified number of rows fetch row is greater than the result set, then fetch all the rows in the result set.
If greater than the specified display row fetched row, show all fetched rows.
If you want to fetch all the rows, but only displays a number of rows, the maximum row count is set to 0, the maximum display line count to the specified value on the line.
Anyway, to understand the meaning of these two parameters can be freely set. But one thing is to note:
When SQL query will be displayed according to the setting below the SQL Results tab Data Studio work space. But browse table data (right-click the table, choose "Browse Data"), will fetch and display all the specified row fetched row. Ignoring the "maximum display line count" setting.
For example, the "maximum row count" is set to 0 (ie fetch all rows), "the greatest display line count" is set to 1000, then proceeds SQL query and browsing data workspace is shown below:
The last point to emphasize is: the value of "maximum row count" should not be set too large, because memory access large amounts of data will affect the performance (in the example fetch all 250,000 rows takes about 1 minute). In fact, the "maximum row count" parameter is equivalent to an additional query fetch first N rows only.
If the maximum row count is 0, then browse the table data is equivalent to execute the SQL statement:
select * from mobile (requires longer execution time)
If the maximum row count is 1000, then the browser time table is the equivalent to the SQL statement:
select * from mobile fetch first 1000 rows only (inquiry be completed soon)