|
View previous topic :: View next topic
|
| Author |
Message |
vadim vashchenko
New User
Joined: 21 Mar 2011
Posts: 13
Location: usa
|
|
|
|
Finally, we are converting to V9 NFM (instead of skip-release to V10 due to our cowardly DBAs).
My question is:
We have a lot of predicates like SUBSTR(COLNAME, 226,8).
It performs poorly. We have two choices. We can split COLNAME into several columns or we can create expression indices on SUBSTR(COLNAME, 226,8) - we have many substrings.
Will we get dissent improvements with the expression indices? What should we take into account? Please share your experience with us.
Thank you |
|
| Back to top |
|
 |
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
Hi Vadim,
| Quote: |
| Finally, we are converting to V9 NFM (instead of skip-release to V10 due to our cowardly DBAs). |
Skip's can done in one of the development environments, if there are a lot. No DBA want's to wake up @ mid-night, seeing an error message saying "SURPRISE!, you didn't expect me, did you!, now suffer my wrath".
Index on Expressions - Its a good thing, but test how much of impact it makes on INSERT and UPDATE statements in batch. If the table is being loaded rebuild would take care of it.
SUBSTR(COLNAME, 226,8) <-- This seems to be a simple sub-string, things can get complicated, if you start doing sub-string on a sub-string and so on...
Thanks,
Sushanth |
|
| Back to top |
|
|
vadim vashchenko
New User
Joined: 21 Mar 2011
Posts: 13
Location: usa
|
|
|
|
Thank you!
That is what I expected: Insert/update might take more resources as well as a build-index phase of the utilities. Again, I appreciate your time. |
|
| Back to top |
|
|
|
|
