terry.home (5/27/2013)
Not a bad suggestion. I have considired this, but not done it.I dont know whether the last six months worth of data is any smaller in comparison to previous.
My original problem was a lack of disk space which caused performance issues. Therefore deleting and shrinking helped to free up some space and allowed the database to respond.
I could potentially now move the last 6 months to a new file, but once this is done, I assume I will still need to get the data older than 6 months deleted.
Am I wrong to think that I will therefore be adding another step into my process but still end up with the same result at the end of the process?
Regards
T
Hi Terry,
Sorry late reply!
Jeff Moden brought up a great point, that you could possibly use Partitioning as a method. Have you looked in that before?
But may be right right adding more complexity than you really want. It might be just as easy to just schedule some type of delete for records older than 6 months if you've already trimemd it down-depending how large it still is/performance of delete operations. It really would depend on your situation, how much down time you can have, and impact to business/users)
--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀