As a rule I would try and avoid using static methods or Singletons with such a facade class, though.
One of the main benefits (for me) of a facade class is that it allows me to easily "swap out" a whole chunk of the system (in this case the real database implementation) for a "mock" version during
unit testing. That way I can easily and quickly check hundreds of different paths through the business logic without incurring the hassle of setting-up/clearing-down data or the time it takes to connect and disconnect to a real database.
I'd pass in a DatabaseFacade object to the Control contructor (or at the very least fetch it from JNDI or some other pre-configured repository).