I found this at the Official SBS blog and while this is not a supported tool, it is an amazing piece of information to have.

A quick snippet from the article states:

[Today's tip comes to us courtesy of Ed Walters.]

Administrators often need to extract a small number of files or even a single file from a SharePoint database, and may not necessarily want to go through the process of an entire disaster recovery to retrieve them.  SharePoint Database Explorer can be useful in cases where you have the database files, but it is inconvenient (or impossible) to restore them to a SharePoint site.  Common scenarios we've seen are:

• A customer has overwritten an important document in SharePoint and no local copy is available; document versioning has not been enabled for the library.  The customer does not want to force users to log off the server during normal business hours.  In this case, you would simply restore the database files from backup, mount them, and retrieve the documents.
• During disaster recovery, if no backups other than the database files exist, we may manually extract the files from the database as a "belt and suspenders" approach to disaster recovery.  This is also useful if there are any concerns about ACLs moving documents to a server in a new domain.  This method is not recommended for extensive disaster recovery procedures where a large number of document libraries must be exported, but we've found it to be sufficient for many SBS deployments.
• A critical change has been made to a document, and the author(s) is not sure of the date the document should be restored back to.  Again, no versioning is in place.  Multiple copies of the document must be recovered for comparison.  It's easier to restore 3 databases and extract the document than it is to restore, mount, and extend 3 SharePoint sites.

One to save for a rainy day!!

ttfn

David