Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

We have a need to fit a database in 4GB in order to use SQL Server Express Edition. I started from a 7GB database, and found a lot of unneeded records, and deleted them. After shrinking, the database size is 4.6GB, and 748 MB is free (according to database properties).

However, when I execute exec sp_spaceused, I have interesting results:

DatabaseName    Database_size   unallocation space
xxxxxx          4726.50 MB      765.42 MB
Reserved        Data          index_size      unused
3899472 KB      1608776 KB    1448400 KB      842296 KB

Any ideas, how can I release at least some of this unused space? Also I know table, which occupied it.

Update: is it worth to trying to rebuild table indexes?

share|improve this question

migrated from Jan 22 '12 at 15:53

This question came from our site for professional and enthusiast programmers.

marked as duplicate by Mike Walsh, Max Vernon, Mark Storey-Smith, Paul White, ypercubeᵀᴹ Nov 24 '13 at 12:35

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

up vote 1 down vote accepted

After index recreation, using this command:


and than I run SHRINK command again - end up with 2.5G database.

share|improve this answer
Using this command for every table, I finally get 1.4G database, which is good enough. – Sergey Osypchuk May 5 '10 at 11:03

First set recovery mode to simple, make backup and shrink all files (data and logs) seprately; use 'move pages to start of database' (or how exactly that is named) option for shrinking.

Then you may consider index defragmenting, helped us in similar circumstances.

share|improve this answer

If you've already shrunk your database, then give DBCC SHRINKDATABASE TRUNCATEONLY a try.


share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.