From: esquel@sommarskog.se   
      
   Tom van Stiphout (tom7744.no.spam@cox.net) writes:   
   > You already got some good suggestions, but to answer your direct   
   > question: no, transaction logging cannot be turned off as far as I   
   > know. As I understand it, it's such a fundamental part of database I/O   
   > that even a switch to turn it off (e.g. when in development mode) was   
   > not possible.   
      
   It is correct, that SQL Server does not offer a way to turn off logging.   
   However, it would be perfectly possible to so. It would probably even be   
   fairly simple to implement. The problem is that people would not understand   
   the implications.   
      
   Many many years ago I worked with DEC/Rdb which had SET TRANSACTION START   
   BATCH_UPDATE. The instruction was clear: this is a non-logged transaction,   
   and if the transaction fails, restore a backup. Later, I was told by one of   
   the developers - he now works for Microsoft and SQL Server - what they did   
   was that they set a bit in the database header, meaning "database corrupt",   
   and whe the transaction was committed they cleared that bit.   
      
   The reason why Microsoft do not offer this option is obvious: there would be   
   no end of misery in this world of people losing their databases, because   
   they don't understand the implications. There's more than enough with people   
   who delete their log files.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Books Online for SQL Server 2005 at   
   http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx   
   Books Online for SQL Server 2000 at   
   http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)