Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #1746
| Newsgroups | comp.databases.ms-sqlserver |
|---|---|
| Date | 2014-04-27 09:08 -0700 |
| References | <ljd3mq$5vr$1@solani.org> <XnsA31A7E40D77CDYazorman@127.0.0.1> <cc8d3248-3d71-4330-bfc7-5fce19b693df@googlegroups.com> <XnsA31AB9D81E3BYazorman@127.0.0.1> |
| Message-ID | <4f6411dd-c6d4-4566-bf75-6adad9c9e50f@googlegroups.com> (permalink) |
| Subject | Re: power loss DB corruption |
| From | bradbury9 <ray.bradbury9@gmail.com> |
El viernes, 25 de abril de 2014 18:16:09 UTC+2, Erland Sommarskog escribió: > bradbury9 (ray.bradbury9@gmail.com) writes: > > > Should not happen if Sql Server is full ACID compilant and it claims to > > > be since SQL Server 2010. > > > > SQL Server 2010? > > > > Anyway, if you pull the powercord in the middle of a big filecopy operation, > > and you run CHKDISK after the operation, are you surprised if errors are > > reported? > > > > > > > > -- > > Erland Sommarskog, Stockholm, esquel@sommarskog.se If fact transaction should be commited after the write in done. In that case the chkdisk should raise no problems which seems to not be the case
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | 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