From: hvdh@gmx.de   
      
   Hi everyone,   
      
   I get database corruption on hard shutdowns and wonder if there's   
   some way to fix this. I googled a lot but couldn't find an answer   
   whether this is supposed to work at all.   
      
   I have a standard consumer PC (single SATA drive on Intel Chipset   
   Controller) running Windows 7 and MS SQL Server 2012 Express.   
      
   When I load the database with transactions and pull the PC power cord,   
   due to ACID compliance, I expect to get no data loss on reportedly   
   completed transactions. However, on SQL Server 2012 very often the   
   database is corrupt afterwards and cannot be used anymore.   
   I tried to disable HDD write caching, but it didn't improve things.   
   On SQL Server 2008, the problem occurred less likely.   
      
      
   ** Can somepoint point me to documentation stating whether MSSQL   
   ** supports ACID (especially the D) compliance on consumer hardware   
   ** and what needs to be configured?   
      
      
   PostgreSQL, InnoDB and others support this as they can be configured   
   to use fsync after each transaction. Does Microsoft also offer this?   
      
      
   Hendrik vdH   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)