- I can make sure my app is in a consistent state.
- I can rollback all the uncompleted transactions if any (just in case) it's ok
- I can DETACH the database
What do I need the log file for after that?
I'm particularly talking about a "highly controlled" environment. So, the real question is: How can I explicitly force everything to be alright in order to avoid possible data loss? Does anyone here have experience doing this kind of operation?
The reason for this is that I'm not a fan of immense log files. The highly controlled environment is my PC running a single app in a single-user mode. I'm the developer of this app and I have complete control over the code changes. I'd prefer to delete rather than
SHRINK so please do not suggest that I simply
SHRINK the file.
UDATE 2 -- PRACTICE
I've had this process in production for more than half a year without any issue.