Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 2 of 2 total |
Execution plan and collations |
Wed, Mar 5 2008 10:20 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Can the execution plan be enhanced to show what type of index is being taken advantage of? I tried a simple query in a not very big table. _name is defined as ANSI_CI, there is one index on it also ANSI_CI I tried 3 formats and got these results where _name = 'homebase' "_name" = 'homebase' [Index scan: 14 keys, 4096 bytes estimated cost] where _name collate ansi_ci = 'homebase' "_name" COLLATE "ansi_ci" = 'homebase' [Index scan: 14 keys, 4096 bytes estimated cost] where _name collate ansi = 'homebase' "_name" COLLATE "ansi" = 'homebase' [Row scan: 185 rows, 51800 bytes estimated cost] For the first two it would be nice if it said something like [Index scan (ANSI_CI): 14 keys, 4096 bytes estimated cost] Roy Lambert |
Wed, Mar 5 2008 10:48 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Can the execution plan be enhanced to show what type of index is being taken advantage of? >> Sure, it's on the list for 2.0 as one of the "minor" items. I'll basically be adding the index name being used for index scans in the plans. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 5, 2024 at 07:30 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |