2017-03-13 51 views
0

需要帮助,以加快下面的执行和优化。查询优化左外连接7个表 - SQL Server

查找附接在2个图像的执行计划.. enter image description hereenter image description here 数据的所有表中如下:

  • 公司 - 25行
  • warranty_period - 878行
  • company_claimtype - 216行
  • claim_type - 25 rows
  • customer - 15980 rows
  • auto_handle - 25行
  • auto_handle_condition - 31行
  • PART_REQUIRED_RETURN - 4521行

下面的查询花了将近12分钟来执行,它仅包含左外连接上述所有表:

select 
    company0_.ID as ID1_9_0_, 
    warrantype1_.ID as ID1_36_1_, 
    partsrequi2_.ID as ID1_20_2_, 
    claimtype4_.ID as ID1_8_3_, 
    autohandle5_.ID as ID1_4_4_, 
    autohandle6_.ID as ID1_5_5_, 
    customer7_.ID as ID1_14_6_, 
    company0_.CREATED as CREATED2_9_0_, 
    company0_.UPDATED as UPDATED3_9_0_, 
    company0_.AUTO_REJECT_USER as AUTO_REJ4_9_0_, 
    company0_.CLAIM_CREDIT_ORDER_HISTORY as CLAIM_CR5_9_0_, 
    company0_.CLAIM_ORDER_HISTORY as CLAIM_OR6_9_0_, 
    company0_.COMPANY_CODE as COMPANY_7_9_0_, 
    company0_.COMPANY_NAME as COMPANY_8_9_0_, 
    company0_.CONNECTED_TO_ERP as CONNECTE9_9_0_, 
    company0_.DEFAULT_CUSTOMER_ID as DEFAULT16_9_0_, 
    company0_.DATE_FORMAT as DATE_FO10_9_0_, 
    company0_.DISPLAY_WORK_LOCATION as DISPLAY11_9_0_, 
    company0_.DISTANCE_UNIT as DISTANC12_9_0_, 
    company0_.ENABLE_SHIPPING_LABEL as ENABLE_13_9_0_, 
    company0_.HANDLE_CREDIT_INVOICES as HANDLE_14_9_0_, 
    company0_.RETURNS_PARTS_DAYS as RETURNS15_9_0_, 
    warrantype1_.CREATED as CREATED2_36_1_, 
    warrantype1_.UPDATED as UPDATED3_36_1_, 
    warrantype1_.COMPANY_ID as COMPANY_8_36_1_, 
    warrantype1_.PERIOD_CONSUMER as PERIOD_C4_36_1_, 
    warrantype1_.PERIOD_PROFESSIONAL as PERIOD_P5_36_1_, 
    warrantype1_.PRODUCT_GROUP as PRODUCT_6_36_1_, 
    warrantype1_.PRODUCT_NO as PRODUCT_7_36_1_, 
    warrantype1_.COMPANY_ID as COMPANY_8_36_0__, 
    warrantype1_.ID as ID1_36_0__, 
    partsrequi2_.CREATED as CREATED2_20_2_, 
    partsrequi2_.UPDATED as UPDATED3_20_2_, 
    partsrequi2_.COMPANY_ID as COMPANY_5_20_2_, 
    partsrequi2_.PRODUCT_NO as PRODUCT_4_20_2_, 
    partsrequi2_.COMPANY_ID as COMPANY_5_20_1__, 
    partsrequi2_.ID as ID1_20_1__, 
    claimtype4_.CREATED as CREATED2_8_3_, 
    claimtype4_.UPDATED as UPDATED3_8_3_, 
    claimtype4_.CATEGORY as CATEGORY4_8_3_, 
    claimtype4_.CLAIM_TYPE as CLAIM_TY5_8_3_, 
    claimtype4_.SORT_ORDER as SORT_ORD6_8_3_, 
    claimtype4_.TEXT_KEY as TEXT_KEY7_8_3_, 
    claimtypes3_.COMPANY_ID as COMPANY_2_10_2__, 
    claimtypes3_.CLAIMTYPE_ID as CLAIMTYP1_10_2__, 
    autohandle5_.CREATED as CREATED2_4_4_, 
    autohandle5_.UPDATED as UPDATED3_4_4_, 
    autohandle5_.[ACTION] as ACTION4_4_4_, 
    autohandle5_.[ACTIVE] as ACTIVE5_4_4_, 
    autohandle5_.[ASSIGN] as ASSIGN6_4_4_, 
    autohandle5_.[COMPANY_ID] as COMPANY_8_4_4_, 
    autohandle5_.[NAME] as NAME7_4_4_, 
    autohandle5_.[COMPANY_ID] as COMPANY_8_4_3__, 
    autohandle5_.ID as ID1_4_3__, 
    autohandle6_.CREATED as CREATED2_5_5_, 
    autohandle6_.UPDATED as UPDATED3_5_5_, 
    autohandle6_.AUTO_HANDLE_ID as AUTO_HAN7_5_5_, 
    autohandle6_.[OPERATOR] as OPERATOR4_5_5_, 
    autohandle6_.[TYPE] as TYPE5_5_5_, 
    autohandle6_.[VALUE] as VALUE6_5_5_, 
    autohandle6_.AUTO_HANDLE_ID as AUTO_HAN7_5_4__, 
    autohandle6_.ID as ID1_5_4__, 
    customer7_.CREATED as CREATED2_14_6_, 
    customer7_.UPDATED as UPDATED3_14_6_, 
    customer7_.COMPANY_ADDRESS as COMPANY_4_14_6_, 
    customer7_.STREET as STREET5_14_6_, 
    customer7_.ZIPCODE as ZIPCODE6_14_6_, 
    customer7_.COMPANY_ID as COMPANY_9_14_6_, 
    customer7_.CUSTOMER_NO as CUSTOMER7_14_6_, 
    customer7_.NAME as NAME8_14_6_ 
from 
    COMPANY company0_ 
left outer join 
    WARRANTY_PERIOD warrantype1_ 
     on company0_.ID=warrantype1_.COMPANY_ID 
left outer join 
    PART_REQUIRED_RETURN partsrequi2_ 
     on company0_.ID=partsrequi2_.COMPANY_ID 
left outer join 
    COMPANY_CLAIMTYPE claimtypes3_ 
     on company0_.ID=claimtypes3_.COMPANY_ID 
left outer join 
    CLAIM_TYPE claimtype4_ 
     on claimtypes3_.CLAIMTYPE_ID=claimtype4_.ID 
left outer join 
    AUTO_HANDLE autohandle5_ 
     on company0_.ID=autohandle5_.[COMPANY_ID] 
left outer join 
    AUTO_HANDLE_CONDITION autohandle6_ 
     on autohandle5_.ID=autohandle6_.AUTO_HANDLE_ID 
left outer join 
    CUSTOMER customer7_ 
     on company0_.DEFAULT_CUSTOMER_ID=customer7_.ID 
+0

我们需要超出图片的计划还有更多,但是您的开局不错。使用[粘贴计划@ brentozar.com](https://www.brentozar.com/pastetheplan/)分享您的执行计划,这里是说明:[如何使用粘贴计划](https://www.brentozar。 COM/pastetheplan /说明书/)。 – SqlZim

+0

也分享创建表/索引条款 –

+0

请在此链接中找到执行计划http://jmp.sh/v/nfHwSoOBi6mIZ6Blo9DA –

回答

0

我发现特别奇怪的是,你从PART_REQUIRED_RETURN得到约585K记录,然后标记那些,但当服务器添加AUTO_HANDLE数据的东西突然多倍至2.1M记录。你确定你的加入会考虑到整个PK吗?当你的查询看起来现在我会认为ID是AUTO_HANDLE的PK,但数字似乎与此相矛盾。在添加AUTO_HANDLE_CONDITION数据时会发生类似的情况。

最后你正在阅读3.3M行或约4.5Gb的数据。我不认为你可以期望把它降低到几秒钟。