Try looking up long running transactions which could be making your log file grow.
The size of the log file for a database in simple recovery mode is dependent on a number of factors like:
- Length of transactions (long running transactions will grow the logs)
- Nature of transactions (transactions with lots of looping before a commit will grow the logs)
- Type of transactions (database maintenance exercises like reindexing huge tables grow the logs)
The best way of understanding your database system is by looking at the transactions which grow so that you're able to identify which ones grow the log most.
Launch SQL profiler to look at the nature of your transactions.
View sessions in SMSS process monitor to see the long running sessions.
Look at tempdb
Query against sysprocesses table (master db) to see the long running queries possibly you could get a hint.
Later on you might realise that your database actually requires more disk spacer because of this nature of transactions.
Also note that choosing the recovery model of your database should not be based on the disk free space available but it should be based on how critical your data is and then let the business buy more space since it has critical data.
Regards,
Chris Musasizi