You just have to add a private constructor to the second approach.
As for the restrictions of approach two: You will never be able to change your implementation to use multiple instances, but since this is a Utility class, this should be okay.
JDBCSupport - An easy to use, light-weight JDBC framework -
If you are worried that the extending class could take the no-instance thing away, no worries... If your constructor is private it will never be possible to instantiate the class, even if another class extends it (well, using reflections,but that's a different story)...
JDBCSupport - An easy to use, light-weight JDBC framework -