Hello, What is performance difference and preference for case insensitive ITSM 8.x implementation?
Did any one had a luxury of comparing and checking the performance of case insensitive implementation of Remedy on top of MS SQL vs Oracle? There are lots of discussions on preference aligned with DBA's availability/preference at specific environment. Are there any hard numbers to what it can be? We are in the position were we can choose between and it comes down to performance of the implementation down the line... There are some discussions about the topic already: https://communities.bmc.com/thread/78151 http://stackoverflow.com/questions/2001165/oracle-11g-case-insensitive-by-default http://geekzspot.blogspot.com/2010/01/case-insensitive-oracle-database.html - there was interesting last comment by the post owner :) Additionally, there are some performance tuning settings like cursor_sharing setting to FORCE because Remedy issues SQL statements with literals, the application could issue thousands of SQL statements. Each statement is treated as a different statement and is parsed. This frequent parsing of the SQL statement uses significant resources such as shared pool and library cache latch, which severely limit performance and scalability with default EXACT. In addition Oracle has a limitation with cursor sharing and case insensitivity. With the Db-Case-Insensitive and Db-Functional-Index parameters, Oracle does not properly use the indexes if cursor sharing is set to FORCE. Therefore, even though FORCE is recommended with normal case sensitivity, if you want to use case insensitivity, have to use EXACT. Is there performance penalty down the line after all ARADMIN indexes are rebuild as function-based indexes? Thank you. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
