Sql Server 2005 model log has reached 93%

I have tried backing up the database and shrinking the model database.  I am unable to figure out how to shrink it down.  The model log is set to 89 MB with 10% unrestricted growth.  Space available shows .08 MB.  The recovery model is set to full.  Autoshrink is not enabled.  Does anyone out there have a solution to this?  
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you tried dbcc shrinkdb('model',20) ?
Chris MangusDatabase AdministratorCommented:
Model should never be growing unless you've grown it manually, or used it.

Model is truly a model for any new database you create via the GUI.

Why are you trying to shrink it?  If it is a problem I'd copy the model .mdf and .ldf from another server.  Stop your SQL service on this server and copy the .mdf and .ldf from the other server over this, then restart SQL services.
CTGSEAuthor Commented:
No I haven't.  Where would I do this from?
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

In management studio.  try this script:

use model

dbcc shrinkdb('model',20)

cmangus is right though...this db shouldn't be growing.  I would say that someone has it as their default db for one reason or another and has been creating objects there.  Just move them to a different db.
Anthony PerkinsCommented:
Before you can do a DBCC SHRINKFILE you are going to have to take care of the Transaction Log.  That means backing it up.

But yes, I agree, you have bigger problems than that.
No need to back up the trans log file for the model database....you probably shouldn't have it in full recovery mode anyway.  Just truncate the log...


It usually isn't advisable to do this, but in this case I think it is OK.
CTGSEAuthor Commented:
I thought I would post back since I am seeking another issue.

Resolution:  I created a maintenance plan to backup the transaction logs to free up unused logs.  This seemed to have helped with many of my clients.  Thanks for all of the replies.
OK, can you close this out?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.