DBCCShrinkDatabase as Security Cleanup Measure?
Recently a private document wasposted to a publicly accessible SharePoint site. The file was deleted and removed from the search index by running an intermediate crawl of the content database. Now the client wants to shrink the database, which is just under a 1Tb in size and sits on a SAN, claiming that this will insure the file is gone. From what I've learned so far this is not guaranteed to really overwrite the address space marked as recoverable. Is there any validity to the notion that shrinking a db is a good way to truly remove the file from Sql Server 2005 (or any sql server maybe) and is there a better method to inusre that a file is truly gone at the byte level?
Software/Hardware used:
sql server 2005, EMC SAN
Software/Hardware used:
sql server 2005, EMC SAN
ASKED:
January 22, 2011 9:38 PM
UPDATED:
January 24, 2011 2:51 PM
Answer Wiki:
Don't see what shrinking the database will do. when you say a document I am assuming that we are talking about a Word document or similar. This won't actually be stored in the database. There will be a pointer in the database to the document which will be in the filesystem.
One point to note is that records aren't actually deleted in SQL Server - the space is marked as available but it might not be overwriiten. if you reoriganise or rebuild the clustered index on the table that would ensure that SQL page was overwritten
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
