>No. Basically, with simple logging you are setting yourself up to rely solely on your database backup for recovery if your database fails. When you restore, you restore to the database that was backed up - you cannot recover any information that may have been in the database after backing up.

That would be good enough for me. Because, if corruption would occur, or something in regards to that, the main goal would be to make sure to recover from something we can rely on. If we would recover from the backup plus the ongoing log after that, we could have a situation that the log would have been corrupted as well during the same timeframe.

>With full logging, theoretically you can recover up to the latest database state that had transactions committed to it because SQL can recreate transactions from the log. If you can't afford to lose time manually recreating data in the event of a crash then full is the way to go.
>
>Auto shrink just means the database physically reclaims empty/deleted record space (knid of like PACK in fox).
>
>Just make sure your database backups, whether done by SQL itself (recommended!!) or by a backup program, are reliable. Make sure you have a policy to check them regularly.

Thanks, I would verify all this today.