November 21, 2006 at 3:22 pm
Forget about SHRINKDATABASE for a minute.
You don't need much space on disk to perform big insert. Much non allocated space inside of mdf file will be quite enogh.
Find out which tables take all your space.
Look at "Table Info" in Taskpad View in EM or run
DBCC UPDATEUSAGE
master.dbo.sp_spaceused 'SuspectedTableName'
If you don't have suspects or everyone is a suspect use sp_MSforeachtable.
_____________
Code for TallyGenerator
November 22, 2006 at 3:09 am
Webproxy log - 276Gb
dbo.blogreport - 39Gb
Tranny Log - 1gb.
I've scheduled a job to run tonight at 2am, failing that I'm escalating the matter, the challenge has been fun but I've got more burning DB issues to address.
Sergei, Ninja, thanks a big bunch guys.
JB
November 22, 2006 at 3:30 am
So, Webproxy log - that's what must take all your attention.
I believe it carries all useless history staff in the worst possible way. I mean fully denormalised.
If you can delete (or move to another database) at least half of this log - you've solved the problem.
_____________
Code for TallyGenerator
Viewing 3 posts - 46 through 47 (of 47 total)
You must be logged in to reply to this topic. Login to reply