Great video. You may not have millions of subscribers like some but the quality of this information is as good as anything else out there on UA-cam. I tip my hat to you good sir ;)
Why? It actually ever simple, you just have an append-only file which you are writing to it the old values of affected rows by every DML operation before applying those changes to actual data pages (the place you read data from). And if you have a crash, then read it in reverse with a rule: if the last appended record for a particular Transaction has COMMIT or ABORT value ignore it else apply those changes to actual data pages.
Great video. You may not have millions of subscribers like some but the quality of this information is as good as anything else out there on UA-cam. I tip my hat to you good sir ;)
Great video! Thank you very much. Finally some good examples
You're going to make me pass my Databases Architecture course...thank you!
Thankyou! this is much more clear and less complicated than my prof made it seem.
you can do farrrrrrrrrrrrrrrrrrrr better than my teacher in the university, thanks for the video, thanks for shining my school life
much thanks for this video the other guy however sounds less robotic
very confusing
lmao
Why? It actually ever simple, you just have an append-only file which you are writing to it the old values of affected rows by every DML operation before applying those changes to actual data pages (the place you read data from).
And if you have a crash, then read it in reverse with a rule:
if the last appended record for a particular Transaction has COMMIT or ABORT value ignore it
else apply those changes to actual data pages.