Be the first to like this
Most Database Administrators choose the BTREE storage structure as a matter of default. It's flexible, accommodates growth , and supports all types of queries- but at what price? Did you know that on average a BTREE takes 100% more i/os than a HASH and 33-50% more I/Os than ISAM (assuming full use of the key)? Did you know that table scanning performance (range searches, pattern matching) gets progressively worse as more and more rows are added (albeit highly dependent on the leading-edge granularity of the used)? Do you know how to prolong the between modifies of a BTREE? If you answered 'No' to any of those questions then read on. Whilst the Ingres BTREE structure works very well for many things, it should not be taken for granted since other storage structures could be more appropriate. When you do use it you should take some time to make sure you are configuring for the best growth and sustained performance/ This paper will tell you how this method will be as effective for you as it has been for us.