Oracle Date in SQL Statement.

Question

Hello,
    We are having performance issues with some reports using conditions on date fields in the Record Selection Formula. Our application does not use the time portion of the date fields very often. When Crystal Reports builds the SQL statement to Oracle it uses a range condition to include all the possible time values. This practice makes a big difference compared to a direct condition
     Example:   SELECT "TABLE_A"."ID"
                       FROM   "TABLE_A"
                       WHERE  ("TABLE_A"."DT">= TO_DATE('2011-03-31 00:00:00','YYYY-MM-DD HH24:MI:SS') AND
                                      "TABLE_A"."DT"< TO_DATE('2011-04-01 00:00:00','YYYY-MM-DD HH24:MI:SS'))
     Is there a way to tell Crystal not to perform range validation on dates?
     We would like to have a SQL Statment that looks like:
                       SELECT "TABLE_A"."ID"
                       FROM   "TABLE_A"
                       WHERE  ("TABLE_A"."DT" = TO_DATE('2011-03-31'))
    We are on Oracle 11 with Crystal Report for VS2010 Sp1.
Thank you.
Charles

Answer 1

Have a look at the kbase below. I think this is a throwback to the fact that we can't handle the milliseconds in the DateTime. So, in order to ensure we get the correct data we search on a range plus one second of what you asked for.
[1217417 - SQL query shows '&lt;' for a DateTime field filter although '&lt;=' was selected |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233313337333433313337%7D.do]