The transaction log for the ARSystem database contains the deleted data... to allow for restoring if the database crashes (and other uses). You can truncate the transaction log file and perform a full backup of the database to clean up the log.
If you can take the database offline for 60 seconds then a very fast way to clear out the transaction log is to detach the database, rename the transaction log file (on disk), then reattach the database. SQL Server will create an empty transaction log file. Users can get back in now. Then - very important - perform a full backup of the database. Stephen -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of L. J. Head Sent: Thursday, April 27, 2006 1:45 PM To: [email protected] Subject: DB Scrub In the DOD arena there are times that data needs to 'disappear'. I was asked by a customer yesterday what options were available for scrubbing of data. I offered the ability to delete records in audit trails and the asked a question I had never even considered. Once Remedy issues the Delete command...and commits the transaction it is deleted out of the table...but what can be done to ensure the data is gone and not just having the pointer to the data removed. Those in government are familiar with the 'military wipe' type of cleaning utilities. We are running SQL Server 2000, are there DB commands that I can run to perform an online compress or something like that? TYIA ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
