Well to provide the answer you are looking for would need much more information, but in short, you need to do some calculations, and then think about what matters to your users.
First - you need to quantify the amount of memory involved here:
How much memory does 1 row take up?
How big can the grid be?
Secondly, given the figure above you need to consider your users needs:
Is the extra memory requirement from (1) going to be a problem? 500Mb is ok for a modern machine, but quite an ask for an older machine. If you're exposing your app within a corporate infrastructure, they will be able to tell you their machine specs.
Does it give you enough of a performance boost to be worthwhile? How long does the data take to gather? How long to transmit/receive. You can reduce the latter by use of compression (easy in IIS7). If it's the former, you should explore server-side caching, and general code/database refactoring.