I have always done the same as Cameron. Although I will add that for epically large datasets, CF's memory management can be lacking when streaming to disk (causing crashes). I was able to manage memory better by writing reports (Excel, PDF, etc) in Java (using POI) where I found garbage collection functioned better with large disk I/O.
--Dawn On Tue, May 28, 2013 at 10:29 AM, Ajas Mohammed <[email protected]> wrote: > Thanks guys. I appreciate your comments. > > <Ajas Mohammed /> > iUseDropbox(http://db.tt/63Lvone9) > http://ajashadi.blogspot.com > We cannot become what we need to be, remaining what we are. > No matter what, find a way. Because thats what winners do. > You can't improve what you don't measure. > Quality is never an accident; it is always the result of high intention, > sincere effort, intelligent direction and skillful execution; it represents > the wise choice of many alternatives. > > > On Tue, May 28, 2013 at 10:16 AM, Cameron Childress <[email protected]>wrote: > >> On Mon, May 27, 2013 at 11:40 PM, Ajas Mohammed wrote: >> >>> Can you share your experience in creating Report Design for HTML reports >>> returning 8000 or more than 8000 records from a DB (query or stored proc). >>> 8000 is just a number I picked. usually our reports return from 10, 100, >>> 1000, 10000 or even more records. >>> >> >> I typically try to steer people to 100 of less records on the page at a >> time for web based reports. Search / pasing works to help reduce the number >> of records on the screen (and sent to the browser) at a time. If they >> REALLY want to see more than about 1000 records on a single continuous >> page, I push for Excel exports, or in a worst case scenario write it out to >> a static HTML file and redirect them there. >> >> At a certain point though, the browser will choke and there is nothing >> really technically that can be done about that. >> >> -Cameron >> > > -- Dawn
