Good idea, but it should be cost effective. Micro$oft licenses is expensive, and since the DB doesn't really demand lots of processors it's no problem running 50+ databases on a...

Changing recovery model is not 'tampering' - but fully allowed. Has impact on performance though.

http://msdn.microsoft.com/library/en-us/adminsql/ad_bkprst_8ik3.asp

http://www.winnetmag.com/SQLServer/Article/ArticleID/8551/8551.html

I solved this issue by setting database properties for /Options/Recovery Model >  'Full'

Maintenance Plans succeeded.

/Henrik