The reports for the client are all static in nature (i.e. they only include data that should be unchanging from past dates).
For example, he's looking for documents created on or between 7/8/13 and 7/12/13 in xyz folder.
When he runs the report and then clicks update the total number keeps growing everytime he hits update for a few minutes. If he waits 10-15 minutes and hits update again the number starts decreasing.
I wasn't able to login to his Db server directly (the tech I was working with is not part of their DBA team and he doesn't have rights on that server) but he did confirm via chat with one of his DBA's that the model of the server is set to simple recovery model.
One thing that threw me off though is that he said the total size is 20 gigs - 18 gig for the mdb and 2 gigs for the t-log. The t-log max size is set to 2 gigs so it's at it's limit. I am the first to admit that I'm not a database expert but 2 gigs on a simple recovery model didn't seem right to me.
We will check on this tomorrow to see what reducing the size does - in the meantime can anyone give me any clues as to where to go with this if neither of these issues help?
(I posted this on the regular forums as well since that's where most traffic is currently, but thought I'd post it here to help build the answers kb.)