Specifying per-table recovery mode I have a table that is used for log data; the data is only INSERTed, never UPDATEd. The table has no business data whatsoever, and thus it is not a problem if I cannot recover it in case of a disaster.

In addition to inserting, I periodically want to empty this table.

The table has no foreign keys, and only one clustered index on the field which contains the log date/time.

The database recovery mode is currently set to FULL. Is it possible to prevent logging transactions when writing/deleting from this specific table, while still logging changes to other tables?
No, logging and recovery don't work at that level. What I recommend is, instead of trying to make one database serve two different recovery objectives, store this logging information in its own database (or a different, existing database) with alternate recovery objectives.

If that is not an option for some reason, the only thing you can really do to minimize the impact on the log is to:


Issue truncate instead of delete - which is still logged, but less so.
Instead of allowing for lots of small inserts, queue those up into batches and do what you can to make the eventual insert eligible for minimally logged transactions.