SQL Server Execution Plan Operators

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 ต.ค. 2024

ความคิดเห็น • 24

  • @shadowitself
    @shadowitself 4 หลายเดือนก่อน

    content that is worth its time :)
    credits for such valuable materials :)
    thx!!!
    btw why You have the Polish emblem (white eagle on red shield) on your laptop? :)

  • @dinudumitrescu8943
    @dinudumitrescu8943 ปีที่แล้ว +1

    Bert, you are a really knowledgeable on this topic and very good on presenting it. Thank you very much.

  • @SaschaDittmann
    @SaschaDittmann 5 ปีที่แล้ว +1

    Thank you for reminding me to take a closer look at the execution plan metrics more often!

  • @lukasziiii
    @lukasziiii 3 ปีที่แล้ว +1

    I've noticed coat of arms of Poland on your computer. Do you have any relationship with Poland? Cheers from Poland!

  • @SB-mq2eb
    @SB-mq2eb 3 ปีที่แล้ว

    Short,Clear and very useful.Amazing thank you so much.just subsribed today

  • @akensturgeon
    @akensturgeon 5 ปีที่แล้ว

    WOW! Great video Bert. I'll have to watch it again as well as the others you've referenced. As for parallelism, you mentioned Cost Threshold for Parallelism indicating that you do not leave it at its default value. What about MAXDOP? Do you typically change MAXDOP or do you usually leave it at its default. Currently our servers still hold the default values for both of those properties which I think we should change; I'm just a little bit leery of doing so fearing that it may cause other issues. I'm under the impression that there's less risk in changing the Cost Threshold than there is with changing MAXDOP. Is that a fair statement?
    Thanks again for all these great videos! I really appreciate them.

  • @prathameshkinareparth
    @prathameshkinareparth 5 ปีที่แล้ว +1

    Hi thanks again for great video .
    Would you mind to show some examples for deciding value of cost threshold p. and Maxdop ??
    Bcz I am currently dealing with more than 100 server and it’s hard to find some best values as each one has different load.
    Also found higher CZPACKET wait under top 5 wait list ...

  • @prathameshkinareparth
    @prathameshkinareparth 5 ปีที่แล้ว

    Covering indexes are the good choice for any key lookup plan .. but always face one issue as one of my table is having almost 184 columns and end users can pick any column in their queries. So end up build many indexes which is very bad practice.
    So what’s your view on this sir ?? SQL version is 2008 & 2012 .
    Waiting for next video ... keep up the good work n thanks.

  • @namanpratyush
    @namanpratyush 5 ปีที่แล้ว

    Great video Bert, very informative.

  • @RomanPeralta
    @RomanPeralta 3 ปีที่แล้ว

    Amazing videos. Great job sharing knowledge.

  • @aloksaxena7905
    @aloksaxena7905 4 ปีที่แล้ว +1

    It would be nice to show database table and actual data. Your videos are really good. But missing something.

  • @jenh3183
    @jenh3183 4 ปีที่แล้ว

    These videos are great! Thanks!

  • @abrahamheredia4854
    @abrahamheredia4854 5 ปีที่แล้ว

    Greath video thanks a lot Berth keep with the good work!,

  • @vladimirpavlovskiy536
    @vladimirpavlovskiy536 2 ปีที่แล้ว

    HI, I have a question, can you please help.
    I have a query which is used when some form opens, it takes about a minute for user to wait.
    I know that system is not using most efficient plan.
    is there any way to force Query Optimiser spend about 1-2 hours to analise all possible way of retriving data so the next time it will use the most efficient plan

  • @virbhadrasutar
    @virbhadrasutar 3 ปีที่แล้ว

    When to use estimated execution plan and actual execution plan?

  • @ramin3809
    @ramin3809 5 ปีที่แล้ว

    Thank you Bert 👍🏼

  • @mooremike44
    @mooremike44 5 ปีที่แล้ว

    Great video.

  • @urlima
    @urlima 5 ปีที่แล้ว

    Thanks Bert

  • @birukarbas5022
    @birukarbas5022 4 ปีที่แล้ว

    my man thanks

  • @BaronJinn
    @BaronJinn 4 ปีที่แล้ว

    Good video but let me rent a little.
    Shit guys, I do not know what is the reason to use SQL Server, everything is OVERCOMPLICATED. Even simple things like creating auto increment field, add index or show DDL how table was created with all indexes/keys ..., almost impossible to do or it takes forever to do. it's a pain in ass.
    Microsoft "Query analyzer" ... Oh my goodness, it is barely understandable, it shows all kind of information except information I needs !!!! In MySQL it's much better and simpler!!!

  • @SHIVANAN-x4r
    @SHIVANAN-x4r ปีที่แล้ว

    Don't show theory..give some practical

  • @23-aa
    @23-aa ปีที่แล้ว

    Bro this one is not with the other four in the ex plan playlist 😢

    • @DataWithBert
      @DataWithBert  ปีที่แล้ว +1

      Thanks for letting me know, I added it.

    • @jerichaux9219
      @jerichaux9219 5 หลายเดือนก่อน

      @@DataWithBertBert: you are my absolute favourite SQL/DB/MSSQL youtuber, bar none. I’ve probably learned more from you about SQL than I have from the countless SO threads, tutorial channels, articles (shoutout to SQLShack, which has pretty consistently good content).
      But, next to you, it is no contest. Thank-you for sharing your voodoo wizardry!