I've implemented log shipping on a development database and all seems
fine. When production goes live, it will incorporate some overnight
and weekly routines that contain TRUNCATE TABLE statements. I
understand that these non-logged operations will cause problems for
log shipping. As I can see it, one option is to replace TRUNCATE TABLE
with DELETE FROM, which will log all the deletes (seems inefficient to
me), while another is to do some sort of database backup after the
overnight job. I'm unclear as to what this would entail. On the other
hand, there might be a much better solution altogether.

Thanks for any tips.

Scott Doughty