Re: top n problem
From: Vlad Vissoultchev (wqweto_at_nospam.myrealbox.com)
Date: 02/13/04
- Next message: Alejandro Mesa: "Re: Update Trouble Using Datetime Range"
- Previous message: Gary Hampson: "Re: Problem inserting into DB2 from SQL Server via Linked Server"
- Next in thread: Steve Kass: "Re: top n problem"
- Maybe reply: Steve Kass: "Re: top n problem"
- Reply: Delbert Glass: "Re: top n problem"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Feb 2004 23:44:59 +0200
> > the point here is that TOP n without ORDER BY is undefined
>
> Pray tell, where does it say that in the documention?
> Are you just repeating mis-information, or did you make that up yourself?
ok,
[ab]use it as you wish. next you can start rewriting those set-oriented
selects using cursors -- it's legal T-SQL syntax :-))
my point here is that everytime a TOP n w/o ORDER BY is used should be
considered a gross hack. there are numerous examples of dubious
selects/updates that [seem to] work but might just stop to under different
conditions.
btw, i get the same gut feeling when a see an IDENTITY property used but
this is OT by far and large...
cheers,
</wqw>
- Next message: Alejandro Mesa: "Re: Update Trouble Using Datetime Range"
- Previous message: Gary Hampson: "Re: Problem inserting into DB2 from SQL Server via Linked Server"
- Next in thread: Steve Kass: "Re: top n problem"
- Maybe reply: Steve Kass: "Re: top n problem"
- Reply: Delbert Glass: "Re: top n problem"
- Messages sorted by: [ date ] [ thread ]