You never disappoint! The plan goes liked this: You send and I receive an email -> I click the link and watch the video -> I learn A LOT! Thank you so very much.
Really really good video!!!!! Please make other videos about optimizing queries. It's really close to what's actually needs to be considered when working in the real tasks.
Interesting video. I was just curious to understand how query costs are getting calculated here. If it's not mili second or second - then what this number actually mean?
The Cost number is an arbitrary number, which means it doesn't represent any length of time or anything else like disk reads. It's a calculation that can be used to compare against other plans on the database.
Yes there is. In Oracle SQL Developer, you can see the execution plan, but it's text based and not a chart or image like this one. Other IDEs will have different ways of viewing the plan.
I wish I were able to get that tool you're using for the flow chart but I can't find it in SQL Server (assuming that's where you're doing this). Is there ever a case to add multiple columns to an index?
Yeah it's a good visualisation. This was done in MySQL Workbench which is using MySQL. SQL Server Management Studio has a similar visualisation, but it's not quite the same. I plan on creating a video like this using SQL Server so you may find that more useful. Adding multiple columns to an index is helpful in some scenarios. One would be if you have an Order By clause with multiple columns, you may want to add those columns to an index as it may improve the performance of the query.
I did not understand how creating index on a temporary table would improve the query. If this operation is conducted every time this query runs, doesn't it increase the cost?
Good point. Yes it would increase the cost as it’s run each time. If it runs slower overall compared to the original method than it may not help. Otherwise a permanent table could be another way to improve it where the index is kept.
You never disappoint! The plan goes liked this: You send and I receive an email -> I click the link and watch the video -> I learn A LOT! Thank you so very much.
Thanks a lot! I'm glad you liked the video.
Really really good video!!!!! Please make other videos about optimizing queries. It's really close to what's actually needs to be considered when working in the real tasks.
Thanks a lot, I'm glad you enjoyed it!
Great demonstration Ben. Very helpful video.
Glad it was helpful!
Great video! Thanks for sharing!
Thanks!
Nice, you made that really easy to understand!
Thanks, I'm glad it was easy to understand!
Interesting video. I was just curious to understand how query costs are getting calculated here. If it's not mili second or second - then what this number actually mean?
The Cost number is an arbitrary number, which means it doesn't represent any length of time or anything else like disk reads. It's a calculation that can be used to compare against other plans on the database.
Very nice and informative, Thank you
Glad it was helpful!
nice video, is there a similar feature (Execution plan and graph representation) in Oracle Database ?
Yes there is. In Oracle SQL Developer, you can see the execution plan, but it's text based and not a chart or image like this one. Other IDEs will have different ways of viewing the plan.
@@DatabaseStar can you please make a video on oracle execution plan how to read it and how know and understand about key improvements?
Sure, good idea!
I wish I were able to get that tool you're using for the flow chart but I can't find it in SQL Server (assuming that's where you're doing this).
Is there ever a case to add multiple columns to an index?
Yeah it's a good visualisation. This was done in MySQL Workbench which is using MySQL. SQL Server Management Studio has a similar visualisation, but it's not quite the same. I plan on creating a video like this using SQL Server so you may find that more useful.
Adding multiple columns to an index is helpful in some scenarios. One would be if you have an Order By clause with multiple columns, you may want to add those columns to an index as it may improve the performance of the query.
I did not understand how creating index on a temporary table would improve the query. If this operation is conducted every time this query runs, doesn't it increase the cost?
Good point. Yes it would increase the cost as it’s run each time. If it runs slower overall compared to the original method than it may not help. Otherwise a permanent table could be another way to improve it where the index is kept.
Great video! Thanks
Thanks!