RM> wahh.. ini saya nggak ngerti. plan terbaik yaitu tanpa plan...
Dalam query sebaiknya tidak menggunakan eksplisit plan. Bila engine
berubah, katakan upgrade dbserver, plan tsb bisa lebih jelek dari
awalnya. Optimasi tidak di plan, tapi struktur DB dan query.
RM> kalo hidup seperti ini.......
Sayangnya hidup tidak punya optimizer. :)
RM> The inner select of a subselect frequently qualifies a number of
Scr implisit, join sudah melakukan filter (yg mana perlu) pada where,
tidak semena2 cartesian product.
RM> If a subselect is automatically transformed into a join, the
RM> access path can differ from that chosen when the join is
RM> explicitly coded. In most cases, it is best to code the join.
Ini maksudnya, kalo joinnya implisit bisa jadi hasil subselect tidak
se-ngejreng dibanding join yg diterangkan dgn jelas. Nah, kelihatan
khan subselect toh ditransformasi jadi join biasa.
Tertanda,
Oguds [36856104]
Berlangganan: [EMAIL PROTECTED]
Stop Berlangganan: [EMAIL PROTECTED]
Keluhan Milis(Unbouncing,spam,dll): [EMAIL PROTECTED]
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/Delphindo/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
