batching with an appropriate non-clustered index seek delete plan (verify based on your batch size - or force it explicitly) can be a HUGE win in large delete scenarios. Depending on what fraction of data you delete it is often a big win to drop other indexes and rebuild them after the deletes are finished.

Gotta take exception to one thing in your article:

1.Data File size - around 1GB initial, 1MB growth increment

2.Log File size - around 800MB initial, 2GB growth increment

Please don't EVER use 1MB growth rate. Devastatingly bad external and internal fragmentation. And for tlog sqlskills.com and kimberly tripp have very good information about tlog size/growth. 2GB growth is suboptimal.