Forum Replies Created

Viewing 15 posts - 16 through 30 (of 133 total)

  • Reply To: Not getting expected index seek.

    Here is all the indexes for the tables. If you need different format, let me know. P.S., the view only creates aliases for some of the columns in the oeordlin_sql...

  • Reply To: Not getting expected index seek.

    I think you're right.  I've found that if I use the LOOP hint to force a loop join, which passes thru the ord_no and line_seq_no thrue to the wspkglin join...

    Attachments:
    You must be logged in to view attached files.
  • Reply To: Nested Join Alternative

    Sergiy wrote:

    It’s funny nobody suggested the most obvious choice in such situation - RIGHT JOIN:

    Select s.Shipment_No
    , p.pkg_no
    ,...
  • Reply To: Nested Join Alternative

    ScottPletcher wrote:

    I would think the subquery would (almost) certainly be able to take advantage of the fact that the query only needs to lookup a single Shipment_No, rather than processing...

  • Reply To: Nested Join Alternative

    This subquery actually seems to work well.  Any ideas if it would have any performance benefits over the nested join query?

    select s.Shipment_No, pl.pkg_no, pl.ord_no
    from wsPKGShipment s
    left join...
  • Reply To: Nested Join Alternative

    ScottPletcher wrote:

    Thanks for that, now I'm clear.

    Yeah, I think the first query you posted should do that.

    As to performance, make sure the s and p tables have an index on...

  • Reply To: Nested Join Alternative

    Let me try to explain what i need better.  I want all shipments, regardless of whether they have matching wsPKG or wsPKGlin records.  I want to join wsPKG records to...

  • Reply To: Nested Join Alternative

    ScottPletcher wrote:

    If I understand your requirements correctly, the code below will do what you want.

    As to performance, make sure the s and p tables have an index on Shipment_No and...

  • Reply To: Nested Join Alternative

    Phil Parkin wrote:

    Might this work?

    select s.Shipment_No, p.pkg_no, l.ord_no  -- You need to get ord_no from either s or p instead
    from wsPKGShipment s
    left join wsPKG p
    ON s.Shipment_No =...
  • Reply To: Best Index Choices

    After rewriting the query and adding new indexes:

    Total Cpu -  1 min 7 sec -> .488 sec

    Total Logical Reads - Over 78M -> 150K.

    Very impressive improvements.  Thanks guys !!

  • Reply To: Best Index Choices

    ScottPletcher wrote:

    The ID is included to make sure the key is unique.  Unique indexes process better in SQL Server.  All key columns from the clustered index are automatically included in...

  • Reply To: Best Index Choices

    ScottPletcher wrote:

    I suggest creating the following indexes to support the query.  If you'd like to adjust other indexes on the tables also, just let me know.

    CREATE UNIQUE...
  • Reply To: Best Index Choices

    Sergiy wrote:

    Can you please run this

    SELECT TOP 10 item_no, loc, COUNT(*) NN
    FROM IMLSMST_SQL
    GROUP BY item_no, loc
    HAVING COUNT(*) > 1
    ORDER BY NN DESC

    and post here the outcome?

                

    July 21, 2021 at 2:14 pm

    #3912474

  • Reply To: Best Index Choices

    Results attached.

    Attachments:
    You must be logged in to view attached files.
  • Reply To: Best Index Choices

    ScottPletcher wrote:

    I can't offer index recommendations without seeing the DDL for the tables, including all current index definitions.  The most critical index is the clustered index, so that should be...

    • This reply was modified 4 years, 4 months ago by Jackie Lowery.
    Attachments:
    You must be logged in to view attached files.

Viewing 15 posts - 16 through 30 (of 133 total)