From: ray.bradbury9@gmail.com   
      
   El viernes, 25 de abril de 2014 12:24:40 UTC+2, Erland Sommarskog  escribió:   
   > Hendrik van der Heijden (hvdh@gmx.de) writes:   
   >    
   > > 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.   
   >    
   >    
   >    
   > If you pull the power cord, there are some risk for incomplete writes,    
   >    
   > isn't there?   
      
   Should not happen if Sql Server is full ACID compilant and it claims to be   
   since SQL Server 2010.   
      
   http://technet.microsoft.com/en-us/library/aa213068(v=sql.80).aspx   
      
   >    
   >    
   > What is important if you want to minimize data loss is to use the full    
   >    
   > recovery model and frequent transaction log backups.   
   >    
   >    
   > Note that if the data file is damaged in case of a power outage, but    
   >    
   > the log file is not, you can recover the database by taking a tail-of-   
   >    
   > the-log backup. If the log file is damaged, the prospects are bleaker,   
   >    
   > even if the database is not.   
   >    
      
   Good point, don't trust totally in ACID compilance. A good backup policy as   
   the above described should always happen.   
      
   Please, note that I am *not* saying that Hendrik is not doing proper backups.   
   -)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)