Question

How can I ensure that all data that I’ve erase from the db tables, is no longer stored in the mdb files (and others) on the hard disk?

Here’s my situation:
My client used to store non-encrypted credit card data, in their database (SQL Server). Thanks to PCI requirements, they now encrypt all that data… However, the mdb file still has some of the old, unencrypted CC written to it.
We’ve verified that there are no more CC’s in the database; we’ve compressed the database; we’ve backed it up to a file and restored it anew, to a new database; we’ve even run sp_cleandb.
Yet, still, when we analyze the persisted file on disk, we still find a handful of non-encrypted CCs – that are not stored in the DB, they’re not part of SPs, views, or UDFs, and they do not appear in any table metadata.

So, my question – how can I ensure all the “bad” CC data is gone? Or, more generally, how do I force MSSQL to store only current data, and clean the file from any “garbage”?

Answer 1

Based on what you’ve done, I’d suggest creating a new database, and moving all your data into that.

That way you know you’re only working with your new data, and no legacy data will somehow be stored in files.