Posted by Alexander Kuznetsov on 03/31/06 04:53

T_MULTILIST.description may be wide. Sorting wide result sets may be
slow. try removing duplicates before joining with T_MULTILIST. Look up
article "The Less SQL Server Sorts, the Faster It Responds"

• Next in forum: ERROR_STATE() Always = 0?
• Prev in forum: Re: Cursor looping versus set-based queries
• Thread view: Re: Can this be optimized? Newbie question

[Reply to this message]