The non-static methods on Database use the CommandTimeout set for the context using the Database.CommandTimeout property. Static methods obviously can't use this, so we should consider adding an overload that takes a timeout. However, consider:
* It's not clear how useful a timeout really is for these types of operation (Delete/Exists)
* It's not clear how often the static methods are used
* It is easy to new up a context and use the non-static methods if a timeout really is needed
* It's not clear how useful a timeout really is for these types of operation (Delete/Exists)
* It's not clear how often the static methods are used
* It is easy to new up a context and use the non-static methods if a timeout really is needed