9:55 not sure how updating a value in row oriented db if the value is bigger than the previous value, will be slower than in column oriented db. Column oriented db will also require other values in the column to be shifted wouldn't it. Also how is a bulk/batch update faster in column oriented db. Each record will still be updated one by one and will require other fields in the column to be moved around for each update.
I can sees that Columnar databases are theoretically slower at OLTP, but with the speed of modern hardware and the fact that the two obvious OLTP processes are small by their nature (i.e. inserting a row from a POS system, or deleting a row, something I prefer not to do -- just mark the row as deleted with a flag), surely this theoretical time penalty is not a real practical limitation on using a Columnar database for OLTP processes? It would be interesting to see a set of real world timings that compared real OLTP business processes conducted on a row based and a columnar based database.
Brilliant explanation; first video that explained how the columns in the columnar database are related across files/blocks. Excellent.
clearest explanation of RO vs CO database so far. thanks!
Pace for this presentation is really good with appropriate short breaks.
Awesome presentation... Thank you so much..
Great presentation, very clear! thanks!
Very good and brief description.
Excellent Presentation and explanation.
Great short presentation!
This is a great video, thanks!
Refreshes my old memory... Thnks
4:17 , Columnar database.
Good job, June!
Excellent explanation
best explanation on internet.
awesome explaination!
Awesome. Thanks.
Great thank you
Very nice
9:55 not sure how updating a value in row oriented db if the value is bigger than the previous value, will be slower than in column oriented db. Column oriented db will also require other values in the column to be shifted wouldn't it.
Also how is a bulk/batch update faster in column oriented db. Each record will still be updated one by one and will require other fields in the column to be moved around for each update.
I can sees that Columnar databases are theoretically slower at OLTP, but with the speed of modern hardware and the fact that the two obvious OLTP processes are small by their nature (i.e. inserting a row from a POS system, or deleting a row, something I prefer not to do -- just mark the row as deleted with a flag), surely this theoretical time penalty is not a real practical limitation on using a Columnar database for OLTP processes? It would be interesting to see a set of real world timings that compared real OLTP business processes conducted on a row based and a columnar based database.
2:05