terry.home (5/17/2013)
Sorry I cannot really answer that.... as the server had been neglected, the backups appear to have failed for some time now.
Might not be a bad idea to setup some backups, especially if it's important data. You could use the SQL Server maintenance plan feature as an option.
Not sure it helps, but I noted as soon as I had cancelled the shrink that had been running a couple of days, the log file backup was much bigger.
Thanks for the info. I've noticed that when running shrink there is some log growth, possible after log grew too when stopping? Good information, I don't use shrink often so that last part is interesting. Documentation on Shrink is not so good online. I wonder if Sybase docs would be better?... Mostly everything on internet just states "don't shrink" not really internals of how it works.
I have been executing must of my commands to this server from a remote machine with SSMS 2008 installed. Today I decided to re-visit sql 2000 query analyser and fired that up on the server in question. I ran the shrink from there but instead of shrinking to 0% free I set it to 50% first.
The shrink ran suprisingly quick and freed up around 10gig. I ran another and this time set it to 40% and this ran quick also. I have now kicked off another delete to run over the weekend.
I feel confident that I will manage to get the space down significantly in this way.
How did it go with shrinking 50% to 40%.. and lower? Did it get progressively slower to shrink as you got closer to the actual data size?
--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀