SQL

"FOREING KEY VIDEOLU DERS" - Tayfur BÖLER from Bookmarklet

"(which should make service packs and upgrades far less painful going forward), the new MERGE statement, star join performance, parallel scans of partitioned tables, and the list goes on. What is the biggest mistake people make when looking at a query plan? I’m not sure about the biggest mistake. What I would do is to encourage everyone to learn as much as possible about how to read query plans, to understand the different types of operators and how they work, and to be careful not to jump to any conclusions before fully understanding a query, schema, and plan. These skills are essential for evaluating whether a query plan is good or bad or whether a better plan exists. There are many things that can go wrong with query plans. For example, a bad plan could be due to cardinality and costing errors, missing indexes, bad join orders, a poor choice of join or aggregation types, too little memory, etc. At the same time, there are few, if any, absolute rights and wrongs. Sometimes scans are better " - Jason Massie