SQL 2008 R2 master.mdf large file size (92GB)

I have a SQL Server 2008 R2 system that is running out of space on the drive.  I have found a master.mdf file that is 92GB in size and I am assuming this is my issue.  I am hoping for some guidance on how we can reduce the file size of this.  I have located under the properties of this an option that is under automatic - Auto Shrink - is set to false.  What impact will this have if I alter this to true and how often and at what times would this run?
Also would there be any other options / command that I can run to reduce the size of this file.
I have limited experience with SQL so would really appreciated the help and guidance in trying to resolve this one.


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.

Deepak ChauhanSQL Server DBACommented:
Please check if you have created any user objects ( Tables) in Master database. 92 GB is unusual size for Master database.

You can shrink the database, follow the MS link step by step.


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
Pawan KumarDatabase ExpertCommented:
Are you taking regular backups ? If not, then take backup and after that you can shrink the database.

For backups, Integrity check etc,.use below Ola's script


You can shrink a DB with 2 ways. Below are the 2 ways given.

-> Shrinking a database by giving a free space percentage

Open in new window

-> Truncate a DB

Open in new window

Vitor MontalvãoMSSQL Senior EngineerCommented:
Autoshrink is a big NO. Never set that to true in any database.
master database shouldn't grow that much so I will also stand for Deepak's observation. Somebody is using master database as a regular user database. And if it's that the case, shrinking it will not solve your problem. The problem should be solved by migrating the user objects to a new database.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Recommendation to close this question by accepting the above comments as solution.
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

From novice to tech pro — start learning today.