Logging enabling

Hi, We have a legacy system running on a non logged databases. We had a server crash and we ended up losing some vital data after the last checkpoint. {aside, I was glad that happened, bcos only then the management will realize how critical is to log the database :-) }. We have now decided to upgrade that system to a logged one. We are not looking for transaction compliance (since we are not using BEGIN WORK AND COMMIT WORK). I am going thru a checklist of what the developers should look for in their code for logging compliance:- 1. Issue a "lock table" before massive deletes. 2. No longer expect dirty reads in case of select-for-update. Is there any other point I should be looking for. thanks. Ravi