The part about the files being generated is true. However, any transactions not committed to the database will be lost. This leads to the possibility of the database being in an inconsistent state and SQL Server refusing to mount it or marking the database as corrupt or "in recovery" until administrative action is taken.
JamesNT
Heartily agree. A small practice with a low transaction rate can *probably* get away with that, but outfits with 10-1000 transactions per second will always have a large trailing "commit queue"
We always stop and grab both.Because data loss, and minimize the O-Sh!t effect.
