[求助]sybase执行计划索引问题求助。
<p>使用执行计划查看的时候其中2张表的使用情况如下:</p><p>其中一张表的索引使用情况是: </p><p> Positioning at index start. <br/> Index contains all needed columns. Base table will not be read. </p><p>而另一张表的使用情况是:</p><p> Positioning by key. <br/> Keys are: <br/> custid ASC </p><p>请问下是不是上面的Positioning at index start.是没有用到索引的?还是什么情况啊?执行的时候效率很低!</p><p></p><p>谢谢了!</p><p></p><p>FROM TABLE <br/> tc_servbaseinfo <br/> b <br/> Nested iteration. <br/> Index : XIE7tc_servbaseinfo <br/> Forward scan. <br/> Positioning at index start. <br/> Index contains all needed columns. Base table will not be read. <br/> Using I/O Size 16 Kbytes for index leaf pages. <br/> With LRU Buffer Replacement Strategy for index leaf pages. </p><p><br/> FROM TABLE <br/> tc_custbaseinfo <br/> c <br/> Nested iteration. <br/> Using Clustered Index. <br/> Index : tc_custbas_17405822582 <br/> Forward scan. <br/> Positioning by key. <br/> Keys are: <br/> custid ASC <br/> Executed in parallel with a 4-way hash scan. <br/> Using I/O Size 2 Kbytes for index leaf pages. <br/> With LRU Buffer Replacement Strategy for index leaf pages. <br/> Using I/O Size 2 Kbytes for data pages. <br/> With LRU Buffer Replacement Strategy for data pages. <br/></p> 没人知道指点下买?? <p>不是没用到索引, 而是上面的用的索引不合理 所以才效率低</p> 来顶一下
页:
[1]