Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ordered scans are not correctly identified in plans #32

Closed
Jorriss opened this issue Apr 25, 2017 · 1 comment
Closed

Ordered scans are not correctly identified in plans #32

Jorriss opened this issue Apr 25, 2017 · 1 comment
Assignees
Labels
Milestone

Comments

@Jorriss
Copy link
Contributor

Jorriss commented Apr 25, 2017

In a pasted plan, the ordered element of a plan operator doesn't show the correct information.

image

In other tools, it does.

image

The plan can be viewed at: https://learnfrom.brentozar.com/pastetheplan/?id=S1uLgYf0l

@JustinPealing JustinPealing self-assigned this Apr 26, 2017
@JustinPealing JustinPealing added this to the 2.0.2 milestone Apr 26, 2017
@JustinPealing
Copy link
Owner

The check for "Ordered" looks for a value of 1 for the Ordered attribute, but this plan uses the value true instead. Looking at the collection of test plans I can see a mixture of both.

There is a similar issue with the Ascending attribute (Issue #35)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants