We have a big problem here. For weeks now, we have been waiting for the
right opportunity to delete calls we have in the database from May and June.
So, last night, at about midnight, I decide to issue the SQL command to
simply remove the records. We don't need them for billing purposes and the
database is simply getting too big.
Unfortunately, after the deletion process goes on for a couple of hours, the
transaction log (which I have now resized to 200 megs) fills up and the
process stops - leaving all of the records that I wanted delete in place.
Of course, once this happens, no one can log in and our phones start
ringing. Even worse, no matter how many times I truncate the transaction
log, it still reports that it has 0.00 megabytes free space.
How in the world is anyone supposed to remove call records or do a call
consolidation when it causes this much chaos?
What can I do to solve this problem? I have 415,000 call records that I
needed deleted. Hell, while I'm at it, I might as well get rid of July as
well, since even six weeks worth of calls seems unmanageable.
Thanks in advance.
David V. Brenner - firstname.lastname@example.org
International Services Network Corporation
For more information about this list (including removal) go to: