I attended session of Pinal Dave and Vinod Kumar on SQL Misconceptions. Few of points from that session is as following
- SET ROWCOUNT and TOP and OrderBy is not same.
- Set RowCount , Top and OrdetBy gives different execution plan
- Misconception is Cluster Index gives the result out in Order. It sort and gives result
- Seems due to parallelism Cluster Index does not gives result in order
- Cluster Index assure u sorted result only if you are explicitly using order by in the query
- Precision of small DateTime 31 sec rounded to next minute and 29 sec gets truncated to orevious minute
- As of textbook cluster index physically store the data.
- Cluster Index does not store in physical order
- Go 10 will run 10 times
- In simple recovery model your transaction log is as big as longest transaction run in the system.
I hope this quick post is useful. Thanks for reading.
Follow @debug_mode
Thank you Dhananjay for this excellent list. Wow – you really paid attention to details.
Nice points. Just thought would share the blog post which I did last year on “Does Clustered Index physically orders the data within a table? – http://vadivel.blogspot.in/2011/09/does-clustered-index-physically-orders.html
–Vadivel
MVP SQL Server
Thanks for doing one of a kind thing at #TechEdIn. This is was an awesome experience to see the love and support. Thanks 🙂 …
thank u sir 🙂