We help IT Professionals succeed at work.

Log Error SQL Server 2008

badrhino
badrhino asked
on
I'm getting an error that I'm not undersanding.  The error is:
Msg 9002, Level 17, State 4, Line 5
The transaction log for database 'database' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

This is where my question begins.  The database is set to simple recovery, I'm not using any commit or rollback statements.  When I go to tasks>Shrink>files and select Log I've only have 1% (log file is restricted at 50mb) available.  It is a samll databse, being used for development and I'm using a lot of delete and drop table statements.

I obviously can keep bumping the file size up and get rid of this error, but I was under the impersion when the database is set to simple recovery, the database did not log.  

I don't care about the log files, so how do I sql from logging on this database?

Thanks!
Comment
Watch Question

Professional Troublemaker^h^h^h^h^hshooter
Commented:
SQL will write EVERYTHING to the log file before it writes to the database... even using simple recovery.  Before the space can be reused, a transaction has to be committed.  I suspect this Microsoft blog might explain it better and more completely than I ever could:

http://blogs.msdn.com/b/sqlblog/archive/2006/09/18/why-is-my-transaction-log-file-growing-rapidly-how-do-i-stop-it-from-eating-up-all-my-disk-space.aspx
Scott PletcherSenior DBA
Most Valuable Expert 2018
Distinguished Expert 2019

Commented:
Please post the output from this statement:

SELECT
    compatibility_level, log_reuse_wait_desc, state_desc, snapshot_isolation_state_desc,
    recovery_model_desc
FROM
    sys.databases
WHERE
    name = '<your_db_name>'

Author

Commented:
compatibility_level:100
log_reuse_wait_desc: Nothing
state_desc: Online
snapshot_isolation_state_desc: Off      
recovery_model_desc:  SIMPLE
      

Author

Commented:
Thanks!