home.social

#queryplan — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #queryplan, aggregated by home.social.

  1. Update to querydiff.com -> mysql now supported!
    - visual diff tree
    - stat table
    - ops list
    - text diff

    Need to provide the JSON format of your query plans, which you can see how to do on the mysql website:
    dev.mysql.com/blog-archive/new

  2. Update to querydiff.com -> mysql now supported!
    - visual diff tree
    - stat table
    - ops list
    - text diff

    Need to provide the JSON format of your query plans, which you can see how to do on the mysql website:
    dev.mysql.com/blog-archive/new

    #mysql #database #queryplan #data

  3. Update to querydiff.com -> mysql now supported!
    - visual diff tree
    - stat table
    - ops list
    - text diff

    Need to provide the JSON format of your query plans, which you can see how to do on the mysql website:
    dev.mysql.com/blog-archive/new

    #mysql #database #queryplan #data

  4. Update to querydiff.com -> mysql now supported!
    - visual diff tree
    - stat table
    - ops list
    - text diff

    Need to provide the JSON format of your query plans, which you can see how to do on the mysql website:
    dev.mysql.com/blog-archive/new

    #mysql #database #queryplan #data

  5. Yo, #sqlserver tuners and optimizers, I have a question: under what circumstances would a #queryplan prefer a scan of a clustered index rather than a seek of a non-clustered index with the same predicate and output fields?

    I've been pouring over query plans lately, trying to reduce pressure of processes in an environment that sees thousands of processes running, with hundreds at the same time, contending for data access, CPU time, and file locks.

  6. Yo, #sqlserver tuners and optimizers, I have a question: under what circumstances would a #queryplan prefer a scan of a clustered index rather than a seek of a non-clustered index with the same predicate and output fields?

    I've been pouring over query plans lately, trying to reduce pressure of processes in an environment that sees thousands of processes running, with hundreds at the same time, contending for data access, CPU time, and file locks.

  7. Yo, #sqlserver tuners and optimizers, I have a question: under what circumstances would a #queryplan prefer a scan of a clustered index rather than a seek of a non-clustered index with the same predicate and output fields?

    I've been pouring over query plans lately, trying to reduce pressure of processes in an environment that sees thousands of processes running, with hundreds at the same time, contending for data access, CPU time, and file locks.

  8. Yo, #sqlserver tuners and optimizers, I have a question: under what circumstances would a #queryplan prefer a scan of a clustered index rather than a seek of a non-clustered index with the same predicate and output fields?

    I've been pouring over query plans lately, trying to reduce pressure of processes in an environment that sees thousands of processes running, with hundreds at the same time, contending for data access, CPU time, and file locks.

  9. Yo, #sqlserver tuners and optimizers, I have a question: under what circumstances would a #queryplan prefer a scan of a clustered index rather than a seek of a non-clustered index with the same predicate and output fields?

    I've been pouring over query plans lately, trying to reduce pressure of processes in an environment that sees thousands of processes running, with hundreds at the same time, contending for data access, CPU time, and file locks.

  10. Currently works for sql server but other flavours of sql should work for the text and xml diff options. Try it at
    querydiff.com/

    Feedback needed!

    4/4

  11. Currently works for sql server but other flavours of sql should work for the text and xml diff options. Try it at
    querydiff.com/

    Feedback needed!
    #sql #database #querydiff #queryplan

    4/4

  12. Currently works for sql server but other flavours of sql should work for the text and xml diff options. Try it at
    querydiff.com/

    Feedback needed!
    #sql #database #querydiff #queryplan

    4/4

  13. Currently works for sql server but other flavours of sql should work for the text and xml diff options. Try it at
    querydiff.com/

    Feedback needed!
    #sql #database #querydiff #queryplan

    4/4

  14. There is also a table under the “statistics” tab where you can sort by cpu, row count etc


    3/4

  15. There is also a table under the “statistics” tab where you can sort by cpu, row count etc

    #sql #database #querydiff #queryplan
    3/4

  16. There is also a table under the “statistics” tab where you can sort by cpu, row count etc

    #sql #database #querydiff #queryplan
    3/4

  17. There is also a table under the “statistics” tab where you can sort by cpu, row count etc

    #sql #database #querydiff #queryplan
    3/4

  18. You just upload or copy paste your query plan as xml and go to the visual tab. Voila! Hover or click nodes to see details

    2/4

  19. You just upload or copy paste your query plan as xml and go to the visual tab. Voila! Hover or click nodes to see details
    #sql #database #querydiff #queryplan
    2/4

  20. You just upload or copy paste your query plan as xml and go to the visual tab. Voila! Hover or click nodes to see details
    #sql #database #querydiff #queryplan
    2/4

  21. You just upload or copy paste your query plan as xml and go to the visual tab. Voila! Hover or click nodes to see details
    #sql #database #querydiff #queryplan
    2/4

  22. I got a bit frustrated trying to compare query plans in sql server management studio so I made a website to do side by side comparisons.
    querydiff.com

    1/4

  23. I got a bit frustrated trying to compare query plans in sql server management studio so I made a website to do side by side comparisons.
    querydiff.com
    #sql #database #querydiff #queryplan
    1/4

  24. I got a bit frustrated trying to compare query plans in sql server management studio so I made a website to do side by side comparisons.
    querydiff.com
    #sql #database #querydiff #queryplan
    1/4

  25. I got a bit frustrated trying to compare query plans in sql server management studio so I made a website to do side by side comparisons.
    querydiff.com
    #sql #database #querydiff #queryplan
    1/4

  26. I got a bit frustrated trying to compare query plans in sql server management studio so I made a website to do side by side comparisons.
    querydiff.com
    #sql #database #querydiff #queryplan
    1/4

  27. Blog alert!

    The sequel to the mystery of why the query didn't go parallel
    Where the heroes of the #sqlfamily shine.
    Thank you Daniel, Cláudio, Fredrik and Bouke for your input!
    #sqlserver #microsoft #dba #queryplan #tuning

    sqlreitse.com/2023/11/11/why-w

  28. Blog alert!

    The sequel to the mystery of why the query didn't go parallel
    Where the heroes of the #sqlfamily shine.
    Thank you Daniel, Cláudio, Fredrik and Bouke for your input!
    #sqlserver #microsoft #dba #queryplan #tuning

    sqlreitse.com/2023/11/11/why-w

  29. Blog alert!

    The sequel to the mystery of why the query didn't go parallel
    Where the heroes of the #sqlfamily shine.
    Thank you Daniel, Cláudio, Fredrik and Bouke for your input!
    #sqlserver #microsoft #dba #queryplan #tuning

    sqlreitse.com/2023/11/11/why-w

  30. Blog alert!

    The sequel to the mystery of why the query didn't go parallel
    Where the heroes of the #sqlfamily shine.
    Thank you Daniel, Cláudio, Fredrik and Bouke for your input!
    #sqlserver #microsoft #dba #queryplan #tuning

    sqlreitse.com/2023/11/11/why-w