Where Do I Want To Go Today? - Bidirectional Indexes
Taking a note from Microsoft's own page, I've decided to share some of my wishes for where I want SQL Server to go. Today.
Meaning this is what I'm looking for now, the things that I'd like to see implemented in future releases. Now I missed the Yukon preview and haven't read too terribly much on it, so I may be asking for something that's coming. If it's not under NDA, let me know.
Otherwise I hope to get some feedback about whether you'd like to see this feature or not. Or maybe you've got something I've forgotten on this feature. Either way let me know. I've got a few and I'm splitting them up to keep comments focused on this one feature. If you've got a wish, send it to me with a description. I'll credit you (if you want) and add my comments before dropping it out there in front of everyone.
Read Both Ways
First of all I'm not sure of the benefits here, but for sure I think this will help more than hurt. MAke the indexes bidirectional. What does that mean? Add a reverse pointer to read both directions.
And make it the default.
Let experienced DBAs only pick one but save the average developer and make the indexes bidirectional by default.
This would allow SQL Server to make a decision about which way to read the index. It might also eliminate some worktables if people want to reverse sort a result set from the way an index is built.
Of course, the Query Optimizer would need to be enhanced, but I'm sure the brilliant SQL Server team wouldn't have too much trouble with this one.
Other items in this series:
©dkRanch.net May 2003