‫All right, Korn's is the thing perfect?
‫No, sir, nothing is perfect, so.
‫So what is the bad thing about partition updates that move rose from one position to another?
‫She's slow.
‫So now updating roads are no longer a straightforward thing.
‫Guys, think about it in a huge table.
‫If you update a rule, you just you go to that.
‫Right.
‫And just updated end of story.
‫But what happens if you update in a in a partition and that the act of updating that rule moves the
‫that that that role from this partition to another partition, let's say customer?
‫It is a bad idea, but let's say Grace, that's an example.
‫We get the grades.
‫I move the grade from partition, Waseca partition one.
‫And I did agree to 60.
‫Now you just move the entire row from one partition to another and that that is a slow the act of updating.
‫Now you're deleting and inserting into another table that could be very, very slow.
‫So so you do this so many times.
‫If you're moving on porchetta other, you can actually harm your SSD.
‫You can.
‫You can of course.
‫Especially you're jumping from one partition to another so that as the pages if you're doing this so
‫many times, man that could hurt Ram.
‫So avoid update.
‫That move arose from one partition to another partition that actually changes the definition of the
‫word.
‫Partition is inefficient.
‫Queries could accidentally scan or partition.
‫So yeah, if you queries actually include the workloads that then knows that, that lets the database
‫know which partition to head.
‫Everything is rosy.
‫However, if you if your query actually is inefficient, you will end up scanning all the partitions
‫and this might actually result in a slower performance than just having a single table.
‫Right.
‫So let's say you select star from this table where it is greater than one.
‫You just basically selected everything.
‫But instead of selecting one table, no selecting seven or five tables based on how many partitions.
‫So the database is jumping between one table and another.
‫So that could be slot.
‫So think about all that stuff, guys.
‫Schema changes are challenging.
‫Dilemmas usually manage that usually.
‫Right.
‫So, like, if you ordered an index on it on the master table or the or the partition table, all the
‫partition child tables will get that index.
‫We saw that.
‫Right.
‫And then the table.
‫However, sometimes this doesn't always work.
‫The tables actually has to support this feature.
‫So that's the interesting part of.