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 |
|
pearsont74
Starting Member
27 Posts |
 Posted - 2007-03-05 : 12:52:01
|
| What does this do and when (if ever) should i use this? |
|
|
spejbl
Starting Member
28 Posts |
|
|
pearsont74
Starting Member
27 Posts |
Posted - 2007-03-05 : 14:21:39
|
| i understand that on a db thats is bein writen to and all on a regular basisthis db is one that we update maybe monthlybut other then that it is only be queried on....so shouldnt shrink help? sorta like compact on access |
 |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-03-05 : 14:30:15
|
| SQL Server's shrink database is nothing like Access' Compact Database. Access' Compact database creates a brand new copy of the database, and only copies over the active data leaving behind any sort space, or temporary tables used for joins and queries. This has the effect of defragmenting and reducing the size of the database file. In SQL Server, all that happens is the file size is reduced. The data in the area being reduced is copied to other parts of the same file wherever there is space for the data. Shrinking a SQL Server database generally results in a highly fragmented table or three, which is generally undesirable. |
|
|
|
|
|
|
Shrink Database?? what is this for