Yes, I see your point, and you are correct. Even under simple recovery, your transaction is logged to facilitate rollback, the server just discards the information once the transaction is done. I've had developers come to me with "transaction log full" error messages, even though the database was using simple recovery. They were processing so much data that they had filled up the log during the transaction, but the error caused it to rollback and then the log got truncated. They only way we knew what had happened was because the growth of the log file had nearly filled the hard drive. Thanks, -- Eric _____________________ "For all its flaws, I would feel safer to have my children grow up in a world dominated by the United States than by any other country." -- Kobsak Chutikul (deputy leader in Thailand), AP news release 3/7/2003
"Robertson-Ravo, Neil (RX)" <[EMAIL PROTECTED]> wrote on 07/26/2006 10:09:18 AM: > Well no, not really. The question was can you prevent it logging calls on > Updates etc - the simple answer is a stone walled no, there are no ifs or > buts here - you cannot do it. To do so would defeat the purpose of using a > database and maintaining its integrity. > > The backup approach is simply saying only bring back what you filter - ALL > of the updates/logs are still within it you just do not restore them. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/SQL/message.cfm/messageid:2531 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:6 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6
