When I look at the execution plan for a SELECT query, the problem is that I have no order in my query, And it seems that the ascending / descending order of sets is being set to the index column used in the query.
Why is this happening, and can it be closed (and should I?)
There are quite a few operations in SQL Server which can be added to the plan without being in the for the Segment Etherator ranking function) Its input is sorted on the Segment column. Do you have any special examples? ORDER BY query.
DISTINCT and
unions will be the reason for getting rid of duplicates in a way.
Group may need to be
sort
group BY column if the scheme has a stream instead of a hash total And there is no appropriate index that pre-ordered the required data.
Comments
Post a Comment