What's impressive is you not only have to put in all the effort and research to discuss a topic, you also have to intentionally craft queries that demonstrate the problems related to it.
SQL Server 2022, along with a recent version of SSMS, features a 'Live Query Plan' button next to the 'Actual Execution Plan' button. This allows the query plan to be visualised in real-time as the query is executed.
It has been around a lot longer than that. I'm not sure why how you came to that conclusion. The problem is that it's quite buggy, causes SSMS to crash, and sometimes plans either never appear, or the wrong plan appears, or the same plan appears multiple times. I tend to not use it at all for those reasons.
If you feel like doing those annotations, go for it. Otherwise, I'm planning on redoing and expanding the training content with the stuff that's here as well.
Cool way to get "under the hood" while the car is going down the highway 😎 Was there a resolution to the single-threaded Index (Eager Spool) operation that would have actually run in parallel like the other Clustered Index operation?
Eager index spools are always built single threaded, likewise the table that the index is built from is read from single threaded. There is no resolution aside from creating the index yourself, if you're on Enterprise Edition.
What's impressive is you not only have to put in all the effort and research to discuss a topic, you also have to intentionally craft queries that demonstrate the problems related to it.
Do what you love and you'll never take a day off!
SQL Server 2022, along with a recent version of SSMS, features a 'Live Query Plan' button next to the 'Actual Execution Plan' button. This allows the query plan to be visualised in real-time as the query is executed.
It has been around a lot longer than that. I'm not sure why how you came to that conclusion. The problem is that it's quite buggy, causes SSMS to crash, and sometimes plans either never appear, or the wrong plan appears, or the same plan appears multiple times. I tend to not use it at all for those reasons.
@@ErikDarlingData Yes sorry, I typed that halfway though watching your video. I must pay more attention! Good video by the way.
The best SQL Server training on internet (EDD) could use some links to these too many great videos as complementary material ;)
If you feel like doing those annotations, go for it. Otherwise, I'm planning on redoing and expanding the training content with the stuff that's here as well.
Cool way to get "under the hood" while the car is going down the highway 😎 Was there a resolution to the single-threaded Index (Eager Spool) operation that would have actually run in parallel like the other Clustered Index operation?
Eager index spools are always built single threaded, likewise the table that the index is built from is read from single threaded. There is no resolution aside from creating the index yourself, if you're on Enterprise Edition.
Should there be a significant execution time difference between the serial v Parallel version? the serial ran in 1m 23s and the parallel in 1m 18s
Yes, I talk about the main reason why in the video too 😘
Hi Erik , will that query work with SQL 2019?
Yes, it may work back to 2016 IIRC, but I can't really try it at the moment.