Advice on how to measure query data size while using DB2?

You will want to optimize the table/view so that the performance is maximized. In addition, remove all columns that are not needed from the table/view/CDT. Using a paging size of 5 or 10 will also reduce the amount of memory retrieved by the query. If none of these options work, then you will have to redesign the Appian application so that the amount of data being retrieved at any one time is smaller. One example I can give is that if you need to display a lot of columns in a grid, design a grid that only shows 7 columns at a time, with links/buttons on the left and right to scroll between active columns of the grid, retrieving only the columns of data for the currently shown columns using queryEntity selection property.

You will want to optimize the table/view so that the performance is maximized. In addition, remove all columns that are not needed from the table/view/CDT. Using a paging size of 5 or 10 will also reduce the amount of memory retrieved by the query. If none of these options work, then you will have to redesign the Appian application so that the amount of data being retrieved at any one time is smaller. One example I can give is that if you need to display a lot of columns in a grid, design a grid that only shows 7 columns at a time, with links/buttons on the left and right to scroll between active columns of the grid, retrieving only the columns of data for the currently shown columns using queryEntity selection property.