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 |
|
Crappy
Starting Member
2 Posts |
 Posted - 2004-03-15 : 08:12:09
|
| Greetings all.I have a FG with two files located on two different drives.When shrinking a file with EmptyFile on a file less than 10GB(±) it works. File is empty and can be dropped.I now have other files which it refuses to do.A shrink ran for 3 days yet the original file stayed the same. 142GB.The other file on the FG is set to auto grow and there was space available.Any idea why this might happen?Cheers,Crispin |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-15 : 12:25:44
|
| Have you run DBCC UPDATEUSAGES to correct any inaccuracies?Tara |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-03-15 : 20:48:57
|
| What kind of disks do you have this database on? I can't believe a shrink ran for 3 days. I would be tearing my hear out. :) If Tara's plan doesn't work, right before you do a full backup, set the recovery type to simple on the database, run a checkpoint, and shrink the files seperately. This should take care of your problem if it's the log files that are large. Can you give us the size of each file?Data: 150gb 100gb used.etc.Also, in addition to the DBCC UPDATEUSAGES, do you run a DBCC CHECKDB regularly?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
Crappy
Starting Member
2 Posts |
Posted - 2004-03-16 : 00:25:54
|
| Hi all,UpdateUsage did not seem to help. Ran forever though :)The problem is not the log files at all but data files.They only way I can move the larger files is create a temp FG and copy the tables to that. Then drop the original file and re-move the tables.EMPTYFILE seems to work then doesn't work. They has to be something stopping it from moving. Ideas?Cheers,Crispin |
|
|
|
|
|
|
DBCC SHRINKFILE with EmptyFile does not seem to w