Ok we just figured out some specifics here. It wasn't our database that was 97 Gb it was the transaction log. We set up jobs to commit the transaction log based on a percentage of the size of the actual database. That fixed the problem. A suggestion here would be for the software to set up a similar condition on the database creation, or include in the documentation, for the user to set similar conditions. The transaction log, for us, was growing pretty fast. Just FYI.