I started a thread in two different private Microsoft newsgroups about minimal logging. There's been a lot of discussion, so now I'm bringing up the issue in public. In an effort to keep things focused, here are guidelines for the discussion:
- This is not being advocated for production machines.
- This is being advocated for testing.
- What is being sought is to be able to quickly delete large amounts of data without bloating the transaction log.
- Think of a delete being more like a truncate when a special keyword or flag is used.
Not everybody thinks this is necessary or a good idea. Others see value in having such a feature.
So, do you want an option to reduce the amount of logging for bulk deletes?
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
About John Paul Cook
John Paul Cook is a Technology Solutions Professional for Microsoft's data platform and works out of Microsoft's Houston office. Prior to joining Microsoft, he was a Microsoft SQL Server MVP. He is experienced in Microsoft SQL Server and Oracle database application design, development, and implementation. He has spoken at many conferences including Microsoft TechEd and the SQL PASS Summit. He has worked in oil and gas, financial, manufacturing, and healthcare industries. John is also a Registered Nurse who graduated from Vanderbilt University with a Master of Science in Nursing Informatics and is an active member of the Sigma Theta Tau nursing honor society. He volunteers as a nurse at clinics that treat low income patients. Contributing author to SQL Server MVP Deep Dives
and SQL Server MVP Deep Dives Volume 2
. Opinions expressed in John's blog are strictly his own and do not represent Microsoft in any way.