得 到现在 还没有11g过
不过哥都被你们忽悠了!我个人观点如下:
不过rowid访问 自然是最快的
1 table access by user rowid
和
2 table access by user index rowid
在访问表时效率差不多的
而两者差别就在 如果有同样的rowid 访问有两次 rowid会更快(top p296)
而同样的访问11g会在result cache中保存说不定,说不定11g快就是这个原因!而10g没有resultcache!
呵呵!
不过哥都被你们忽悠了!我个人观点如下:
不过rowid访问 自然是最快的
1 table access by user rowid
和
2 table access by user index rowid
在访问表时效率差不多的
而两者差别就在 如果有同样的rowid 访问有两次 rowid会更快(top p296)
而同样的访问11g会在result cache中保存说不定,说不定11g快就是这个原因!而10g没有resultcache!
呵呵!
Rowid Access
The most efficient way to access a row is to directly specify its rowid in the WHERE clause. However,
to take advantage of that access path, you have to get the rowid first, store it, and then reuse it
for further accesses. In other words, it is a method that can be considered only if a row is accessed
at least two times.
The most efficient way to access a row is to directly specify its rowid in the WHERE clause. However,
to take advantage of that access path, you have to get the rowid first, store it, and then reuse it
for further accesses. In other words, it is a method that can be considered only if a row is accessed
at least two times.
However,
to get the rowid first, store it will be 11g rc!so why rowid access quick swift fast 10g rowid access。
to get the rowid first, store it will be 11g rc!so why rowid access quick swift fast 10g rowid access。
this is it!
-----------end-------
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/13750068/viewspace-722942/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/13750068/viewspace-722942/
本文深入分析了Oracle 11g中Rowid访问的高效方式,对比了Rowid访问与传统访问方法的性能差异,并解释了Rowid访问为何在某些情况下能提供更快的速度。通过理解Oracle 11g的内部机制,读者可以优化查询性能,提高数据库操作效率。
1029

被折叠的 条评论
为什么被折叠?



