Re:VAXen, My Children, Just Don't Belong in Some Places
by jmalicki on Sunday August 31, 2014 @11:07PM
(#8251342)
If your database is ACID, you can pull the power on the server from the wall and have it instantly turn off w/o data loss. That's the entire point of transactions...
Re:VAXen, My Children, Just Don't Belong in Some Places
by newman314 on Sunday August 31, 2014 @11:45PM
(#8251441)
If your DB is ACID AND your underlying storage has not lied to you about committing the write...
Re:VAXen, My Children, Just Don't Belong in Some Places
by CaptainZapp on Monday September 01, 2014 @07:59AM
(#8252430)
This is the basic reason why raw devices where the way to go for decades for use as database devices and are still in use in most installations.
I'm talking about Sybase here. But any database, which shifts the commit responsible to the operating system (without explicit guarantees that committed data is indeed written to disk) may invite you in for a huge and very unpleasant surprise.
Re:VAXen, My Children, Just Don't Belong in Some Places
by newman314 on Tuesday September 02, 2014 @06:21AM
(#8256773)
Counting on raw devices when you have a SAN underneath presenting LUNs to the server means unless you are very careful, it does not mean that said write necessarily made it all the way onto disk.
Re:VAXen, My Children, Just Don't Belong in Some Places
by lutusp on Sunday August 31, 2014 @11:14PM
(#8251358)
> If your database is ACID, you can pull the power on the server from the wall and have it instantly turn off w/o data loss.
Yes -- all except the ongoing transactions at the users' workstations. That by itself could represent a serious synchronization problem. For a serious business, an emergency power system might represent a better choice.
Re:VAXen, My Children, Just Don't Belong in Some Places
by dllthomas on Monday September 01, 2014 @02:29PM
(#8254119)
If you've not pulled the plug on your users' workstations, the clients should be perfectly capable of retrying the broken transactions when the database comes back up. There can, of course, be constraints that make this impossible, but sloppy coding making it impossible is more common.
To assure data integrity, an interactive database system has to log off all its users and shut down open databases before rebooting. If the reboot can't be orchestrated that way, if users can't be logged off in an orderly way, there will be data loss.