Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-13 : 09:54:37
|
| Nataly writes "The size of data file is 6.1 Gb but it show that in use only 5 G.Shrinking doesn't reduce it.Please, what to do?" |
|
|
Kevin Snow
Posting Yak Master
149 Posts |
Posted - 2002-05-13 : 13:49:32
|
| Two things may help. One, is designating how much free space should be in the files after shrinking. Another, is moving pages to the beginning of the file before shrinking. SQL likes to have elbow room, and constricting the database size too low will affect performance. Moving pages to the beginning is certain to affect the performance as well.Make sure you refresh your enterprise manager and/or update statistics if you don't see the change you expected. I tested this on a 3 GB database with 300GB free space set to 1% free space after shrinking. It successfully shrunk to 29GB free.If this still doesn't work, you might check your indexes for a low fill factor, or high fragmentation percentage (at least on your largest tables). This is valid for the .mdf. Remember, shrinking the log file is a different ballgame. |
 |
|
|
|
|
|
Size of .mdf file