This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Hi all, I'm currently designing a database and I'd like to get some suggestions on the following--when parsing the results of a query, is it most efficient to have a ResultSet with several rows (few columns), or one with few rows and many columns? Is the ResultSet stored as doubly-linked list? Thanks for any suggestions, ::WS [ June 09, 2003: Message edited by: Winston Smith ]
for (int i = today; i < endOfTime; i++) { code(); }
SJ Adnams
Ranch Hand
Joined: Sep 28, 2001
Posts: 925
posted
0
I think you'll find that the database works better with narrow tables (few columns, lots of rows). I'm fairly sure that DB2 uses a different algorithm once a query exceeds a certain number of columns (20ish? ) which causes a slowdown. That said, it's better not to limit your whole database design by a single possible performance hit.
Winston Smith
Ranch Hand
Joined: Jun 06, 2003
Posts: 136
posted
0
Thanks, Simon. I've been dredging through Oracle's technical manuals and found little info on this, but I'll give both schemes a try and post the results. ::WS
0
