John Mitchell-245523 (3/20/2013)

---

There's a limit to how small you can shrink a database. I can't remember off the top of my head what it its - I think it's either the size of the model database or the size of the database when it was created?

Why do you want to do this, anyway? If you shrink the database, it will only grow again, unless you're going to set it as read only.

John

Bobby Glover (3/20/2013)

---

Are you talking about a production db. I would not shrink a production db POINT BLANK.

Bobby Glover (3/20/2013)

---

The auto grow setting on the db has been triggered at some point and the file/s have been extended. Allowing data to be written into the free space. If you shrink it the db will grow again anyway. If you lower the setting it will extend the file more frequently at a cost of performance each time.

Make sure the auto grow is set to an appropriate amount of MB and not %. All dbs should have a decent amount of free space to grow into.

See it like this: Its the same as buying clothes for small children. You never buy clothes that just fits today always buy the size up so they can grow into it.

SQL ORACLE (3/20/2013)Shrinking the database such that it has zero available space is requested by our users. They use ithe database for creating reports.

Unfortunately, I am asking a solution not asking why I want to do so.