Dealing with a 4rd party application that inserts into its log table, but watching sql profiler i see a ton of the same traffic. Its trying to insert into the table, but generates an error that mentions the transaction log for that DB is full.
Well, earlier I had reset the recovery mode to simple, from full since this is a test system and dont really care about recovery.
So the message mentions to check the log_reuse_wait_desc column in sys.databases and there the value is 'CHECKPOINT'. At least at that point in time.
There is plenty of space in the transaction log and the physical disk has plenty of space as well.
What could be causing the error that seems to suggest the transaction log is full, when in fact it is not?