Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1739
| From | Hendrik van der Heijden <hvdh@gmx.de> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | power loss DB corruption |
| Date | 2014-04-25 09:43 +0200 |
| Organization | solani.org |
| Message-ID | <ljd3mq$5vr$1@solani.org> (permalink) |
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
Back to comp.databases.ms-sqlserver | Previous | Next — Next in thread | Find similar
power loss DB corruption Hendrik van der Heijden <hvdh@gmx.de> - 2014-04-25 09:43 +0200
Re: power loss DB corruption Erland Sommarskog <esquel@sommarskog.se> - 2014-04-25 12:24 +0200
Re: power loss DB corruption bradbury9 <ray.bradbury9@gmail.com> - 2014-04-25 04:42 -0700
Re: power loss DB corruption Erland Sommarskog <esquel@sommarskog.se> - 2014-04-25 18:16 +0200
Re: power loss DB corruption bradbury9 <ray.bradbury9@gmail.com> - 2014-04-27 09:08 -0700
Re: power loss DB corruption rja.carnegie@gmail.com - 2014-04-25 06:54 -0700
Re: power loss DB corruption Graeme Geldenhuys <graemeg@example.net> - 2014-07-02 22:28 +0100
csiph-web