Database 'model' transaction logs are full and I can't start SQL...

SQL will start right now and then stop about 3 seconds after and I see the following entry in the event viewer:

The transaction log for database 'model' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

However, I can't go into the management studio or anything because it's won't allow it to start long enough for me to connect. How can I empty the transaction logs for 'model' without being in SQL management studio to run a query?

This is SQL 2005 by the way...
LVL 1
willlandymoreAsked:
Who is Participating?
 
Ryan McCauleyConnect With a Mentor Data and Analytics ManagerCommented:
The "Model" database is what SQL Server uses as the baseline for creating new databases - it doesn't have any actual data in it. If you have another copy of SQL Server elsewhere on your network (as long as it's the same version or lower), you can just replace the model.MDF and model.LDF files with the ones from the other server, and then SQL should start without a problem.

If you don't have another SQL Server instance handy, you'll need to rename the log file, then start SQL Server (which will flag the model database as "Suspect", since the log is missing). Once it does that, you can ask SQL Server to recreate the log file from scratch. See this link for instructions on recreating a log file when it's missing:

http://www.tech-recipes.com/rx/1867/sql_server_2005_how_to_attach_or_reattach_a_database_missing_the_ldf/
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.