Hi Megistal,

I'd be interested to learn why you'd like another way to force log truncation, other than temporarily switch the database to SIMPLE? It's true that the techniques you suggest are now deprecated.

If you surf around you'll probably find reference to an alternative, which is BACKUP LOG TO DISK='NUL'. However, it's a very bad practice. It basically takes a log backup and just discards the contents, without SQL Server being aware of the fact. You can continue to take normal log backups after this but they will be useless as the log chain is broken. Jonathan Kehayais covers this well in Chapter 8 of his "Troublshooting SQL Server book[/url]" (the eBook is currently a free download).

Cheers,

Tony.