Posted by Simon Hayes on 09/26/05 20:32

Rick wrote:
> I'm not so sure it isn't a bug.
> Here are some observations.
> If I write a select statement like
> 'Select * from mytable order by datecolumn, intcolumn', the int column
> order is correct.
> If I write a select statement like
> 'Select * from mytable order by datecolumn desc, intcolumn', the int
> column order is not correct.
> This parallels the (mis) behaviour of the clustered index.
> Is there a logical reason for this or is this a bug?
>

I suggest you post a CREATE TABLE/INDEX and INSERT script which
reproduces the issue (and of course your MSSQL edition, version and
servicepack), otherwise we have to make guesses about what your table
structure, data and query look like. It's not really clear from your
description what you're seeing, nor what you consider correct behaviour
to be in this case - if you provide something which can be copied and
pasted into Query Analyzer, you'll probably get a better response.

http://www.aspfaq.com/etiquette.asp?id=5006

Simon

• Next in forum: Re: SQL Server Hanging
• Prev in forum: Re: Finding the most recient datetime
• Thread view: Re: ordering an int column

[Reply to this message]