Symptom
Adaptive Server Enterprise (ASE) optimizer does not consider any index scan for equality and non-equality comparison of an encrypted datetime column to a constant value.
Example : where encr_datetime_col = '1988/12/31'
Even if the encrypted column 'encr_datetime_col' is the first column of an index, ASE optimizer does not consider that this predicate is a search argument, and the index scan is never used.
This is because the left node and right node have different data types. In the above case, encr_datetime_col is a datetime data type column and '1988/12/31' is a constant value treated as a character data type.
Read more...
Environment
- SAP Adaptive Server Enterprise version (ASE) 15.0
- SAP Adaptive Server Enterprise version (ASE) 15.5
- SAP Adaptive Server Enterprise version (ASE) 15.7
Product
Keywords
encrypted column, datetime , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.