Re: Left Join and Order by
- From: "Carlos Sacristan" <nomail@xxxxxxxxxx>
- Date: Fri, 7 Aug 2009 08:29:32 +0200
Anyway, the way the table is ordered on disk is also logically (with double-linked list) when it has a clustered index.
So, depends point of view, you can talk about order or not... I feel more agree with Tibor
--
-----------------------------
"Caminar sobre el agua y desarrollar software a partir de unas
especificaciones es fácil, si ambas están congeladas."
Edward V. Berard, ingeniero informático
http://blogs.solidq.com/es/elrincondeldba
"RickNZ" <kiessig@xxxxxxxxxxxxxxxxx> wrote in message news:B2B947DE-9459-4F23-93BB-C26381FB3F5C@xxxxxxxxxxxxxxxx
Correct. A table isn't ordered. You define the order for rows when you
return data from a table, using the ORDER BY clause.
Well, not strictly true.
An ORDER BY clause certainly doesn't change anything in the way a table is
ordered on disk. However, if a table has a clustered index, then it
definitely is ordered on disk, based on that index. In that case, the order
determination is made at insert or update time, not at select time.
--
Check out my upcoming book: ASP.NET: Building Ultra-Fast and Ultra-Scalable
Websites Using ASP.NET and SQL Server
.
- References:
- Left Join and Order by
- From: Michael
- Re: Left Join and Order by
- From: Carlos Sacristan
- Re: Left Join and Order by
- From: Michael
- Re: Left Join and Order by
- From: Uri Dimant
- Re: Left Join and Order by
- From: Michael
- Re: Left Join and Order by
- From: Tibor Karaszi
- Re: Left Join and Order by
- From: RickNZ
- Left Join and Order by
- Prev by Date: Re: Left Join and Order by
- Next by Date: Re: losing connection with application role
- Previous by thread: Re: Left Join and Order by
- Next by thread: Re: Left Join and Order by
- Index(es):
Relevant Pages
|