Class design for DB code

Hi this is really not a Java specific question but more in regards to OO 
design in general.  I have an application which has access to multiple 
tables in a database and a multitude of different SQL statements for 
manipulating the many tables and retrieving data from them.  The part I am

struggling with is a good class design for the Java code which deals with 
the DB.
I would like to achieve the following:
1. Separating DB code from the main application code.
2. Reducing code redundancy
3. Managing SQL statements in a good way.

For the most part I can deal with items 1 and 2, however the managing of
SQL 
statements is the part that gets me.
There will be a huge number of different SQL statements needed for this 
project.
However to create a means of dynamically creating SQL statements can
become 
a bit over-complicated.
I also don't like to see a class filled with hard-coded SQL strings
waiting 
to be called, but it looks like it's the most practical means.

I am quite new to dealing with DB and although having used it before it
was 
rather sparce use of it.

If anyone knows my situation and can give me some advice I'd appreciate
it. 
If you need me to further clarify or give more info please let me know.

Thank you,
Peyman M.