2016 Service Pack 1 Performance - SLAbase table and additional index cndx_PrimaryKey_SLAid

Hi,

Since upgrading to 2016 Service Pack 1. We've seen frequent "SQL Timeout" errors. This has been traced back to one significant additional SQL cost during query executions in multiple cases. The inclusion of dbo.SLAbase joins across Contact, Company and Lead SELECT's. We have disabled SLA and Enhanced SLA feature introduced in Service Pack 1, but there is still a large execution cost with querying the FilteredViews.

For example, from within the SQL Execution plan for one query we see mentions of SLABase table, SLAId and SLAInvokedId relationships and a:

                              <NestedLoops Optimized="false">
                                <Predicate>
                                  <ScalarOperator ScalarString="[HIDDEN].[dbo].[LeadBase].[SLAInvokedId]=[HIDDEN].[dbo].[SLABase].[SLAId] as [sla_lead].[SLAId]">
                                    <Compare CompareOp="EQ">
                                      <ScalarOperator>
                                        <Identifier>
                                          <ColumnReference Database="[HIDDEN]" Schema="[dbo]" Table="[LeadBase]" Column="SLAInvokedId" />
                                        </Identifier>
                                      </ScalarOperator>
                                      <ScalarOperator>
                                        <Identifier>
                                          <ColumnReference Database="[HIDDEN]" Schema="[dbo]" Table="[SLABase]" Alias="[sla_lead]" Column="SLAId" />
                                        </Identifier>
                                      </ScalarOperator>
                                    </Compare>
                                  </ScalarOperator>
                                </Predicate>

This part of the query execution is referencing this index: cndx_PrimaryKey_SLAid.

In 2015, running the same query against "FilteredLead" and "FilteredContact" the resulting execution plan does not include any reference to SLAId or the SLABase table, and therefore no timeout limits are hit at the current setting.

I have seen a mention of a performance tweak made in this report to the SLABase table, along with other generic improvements for a benchmark test and a mention of a fix to be made available in Service Pack 1.1:

- When will Service Pack 1.1 be released?

- Is there a patch fix available until then?

- Is there a workaround to remove these relationships, or improve query execution?

Thanks,

James