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 |
|
Afroblanca
Starting Member
9 Posts |
 Posted - 2005-07-29 : 13:01:02
|
| I'm currently in a situation where I'm trying to shrink a DB and it's taking a real long time. This is sort of an extreme example - the DB size is 217GB, and only about 35GB are actually in use. This is the thing - I tell it to shrink the DB, and after a while it does that lovely Windows thing where everything inside the window "blanks out." The drive light isn't flickering much. Task manager says that the application is "not responding," and when I do an sp_who 'active', the process is apparently "sleeping."So, I'm thinking, "Ok, this locked up." I check the CPU utilization in task manager, and it's averaging around 20-25%. However, after I cancel the process, CPU utilization goes down to about 5%. So it's obviously doing something.What should I do? Just let it run? Is it bad to use the DB while it's shrinking? |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-07-29 : 13:53:26
|
| Is most of the space in the Log, or the Data file?If its the LOG you can just "truncate" that which, whilst a bit brutal, will be quick.Kristen |
 |
|
|
|
|
|
Having trouble shrinking an SQL 7 DB