I appreciate the explanation and example! Watching this in 2025, it's amusing to note that we've surpassed your last projected future year by five years. 😊
Hi partition was created still year 2020 so what will be the case when years is 2021 and so on ? Do we need to again create partition for 2021 year or sql will automatically create so ?
Decent example.... It's much easier just: Aggregating by partition. Daily rows in a year 365 with sum(sales) .. 365 rows. Partition by year = 1 row (total sum sales in year). It's literally that simple. Don't screw up your table aggregates step 1 lol. Other than that you are literally removing rows from being scanned. For example non partition youd literally scan sum of sales x365 times. New partition by you scan 1. Super simple example but imagine how faster and processing power that takes.
I appreciate the explanation and example! Watching this in 2025, it's amusing to note that we've surpassed your last projected future year by five years. 😊
Thanks for the explanation and example! I'm watching this in 2020, which coincidentally is the last future year you planned for. =)
Great video! So many things I would have changed in the past with this technique.
Nice. It would have been cool to see you execute code to see how much faster Partitioning is
Wonderful summary! Saved me a lot of time! Thank you!
Thank you for the explanation and examples
Thank you for the video. Very good explanation.
Hi partition was created still year 2020 so what will be the case when years is 2021 and so on ?
Do we need to again create partition for 2021 year or sql will automatically create so ?
Saved me a lot of time with this unreal fking partition. I have problems with this indexes microsoft documentation didnt help
great explanation men, thanks a lot
Very good explanation!
Can you go over horizontal and vertical partitioning? I am having difficulty understanding them
how is this functionally different than an index on the year?
Great explanation.
Decent example.... It's much easier just: Aggregating by partition. Daily rows in a year 365 with sum(sales) .. 365 rows. Partition by year = 1 row (total sum sales in year). It's literally that simple. Don't screw up your table aggregates step 1 lol. Other than that you are literally removing rows from being scanned. For example non partition youd literally scan sum of sales x365 times. New partition by you scan 1. Super simple example but imagine how faster and processing power that takes.
Thank u bro. U r only one who explained this shit
Can you query each of the file group and see their data?
Yes. U can query using the filegroup