• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Compressing returned data from Oracle

 
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Does anyone have any experience with reducing the size of the data set returned from a database (Oracle) query by (for example) XML-encoding the result set in a stored procedure, thereby converting the data into string format, then ZIP-compressing the XML, and then returning the zipped data (possibly base64-encoded)?
I have a case where the potential upper limit to the returned data set is about 4.5 megabytes (in raw text format), which could potentially compress to about 1-5% (say around 100k) -- this would be much quicker to return from the database to the application server. (In our case, the database is on the other side of the planet, too.)
Any other hints on optimising large result sets? Or is it still most efficient to use ResultSet -- does the Oracle driver compress the data along the way?
There is very considerable complexity added by zipping and base64-encoding (assuming you already have a stored procedure in any case.)
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic