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 |
|
bassem_farouk
Starting Member
18 Posts |
 Posted - 2010-05-26 : 03:30:23
|
| Hii have a nightly everyday job that shrinks my database the shrink usually took 5 to 7 hoursi have a report which need to be run in a specific time(can't wait for shrink to finish), if the shrink took too long time , the report throw errors,any solution for that? is shrink is online operation, how can i minimize the effect of shrink on my report?ThanksThanks |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-05-26 : 05:16:12
|
| You should NOT shrink a database - except if you have made a one-off deletion of stale data, or an accident has caused much-larger-than-normal transaction log growth.Shrinking the database causes it to need to then regrow, which causes fragmentation of data within the database, as well as at the file-system level, which reduces performance. |
 |
|
|
|
|
|
shrink DB cause report error