What is the best way to work with large databases in Java depending on context?
Posted
by
user19000
on Programmers
See other posts from Programmers
or by user19000
Published on 2011-03-02T11:33:40Z
Indexed on
2014/06/04
21:41 UTC
Read the original article
Hit count: 153
We are trying to figure out the best practice for working with very large DBs in Java.
What we do is a kind of BI (business Intelligence), i.e analyzing very large DBs, and using them to create intermediate DBs that represent intelligent knowledge of the DBs.
We are currently using JDBC, and just preforming queries using a ResultSet.
As more and more data is being created, we are wondering whether more appropriate ways exist for parsing and manipulating these large DBs:
- We need to support 'chunk' manipulation and not an entire DB at once(e.g. limit in JDBC, very poor performance)
- We do not need to be constantly connected since we are just pulling results and creating new tables of our own.
- We want to understand JDBC alternatives, with respect to advantages and disadvantages.
- Whether you think JDBC is the way to go or not, what are the best practices to go by depending on context (e.g. for large DBs queried in chunks)?
© Programmers or respective owner
