Home Dashboard Directory Help
Search

missing_join_predicate event: behavior and description by Ana Mihalj


Status: 

Closed
 as Duplicate Help for as Duplicate


1
0
Sign in
to vote
Type: Bug
ID: 693321
Opened: 10/6/2011 3:51:08 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Description of missing_join_predicate event is: "This event only occurs if both sides of the join return more than one row."

From BOL (http://msdn.microsoft.com/en-us/library/ms175146(v=SQL.110).aspx): This event is produced only if both sides of the join return more than one row.

But missing_join_predicate event is produced if one side of join returns one row; it will be produced even when both side of the join returns only one row.

So behavior or documentation isn't correct.
Details
Sign in to post a comment.
Posted by Microsoft on 1/30/2012 at 1:43 PM
Dear Ana,

We're closing this as a duplicate.

Best regards,
Eric Hanson
Program Manager
SQL Server Query Processing
Posted by Microsoft on 10/16/2011 at 8:21 PM
Dear Ana,

Thanks for the suggestion. We'll change the code to ignore the number of rows and issue the warning if there is no join predicate regardless of cardinality estimate. This will appear in a future relase after SQL Server 2012. We've also updated the documentation to remove the statement that "This event only occurs if both sides of the join return more than one row."

Best regards,
Eric Hanson
Program Manager
SQL Server Query Processing
Sign in to post a workaround.