SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 59871: When using a numeric value instead of a date constant to subset a DBMS table, unexpected results or performance problems occur

DetailsHotfixAboutRate It

Incorrect results or a performance problem might occur when the following conditions are true:

  • You are accessing at least one database management system (DBMS) table via a LIBNAME statement.
  • Your SQL query contains a WHERE clause that is comparing a date variable using the BETWEEN operator.
  • The date variable is being compared to an internal SAS® value for a date variable (such as the number of days since 01JAN1960) instead of using a SAS date constant.
  • Your SQL query triggers implicit pass-through.

Incorrect results occur when a DBMS allows the comparison of a date variable with a number, and the number is not interpreted as the intended date. 

Performance problems occur when a DBMS does not allow the comparison of a date variable and a number because the data types are not compatible. In this scenario, the query is partially processed by the DBMS and partially processed by SAS. This performance problem is especially apparent if the SQL query contains a join of two or more DBMS tables, because the join and the subsetting are done in SAS rather than in the DBMS.

The workaround is to use a SAS date constant instead of the number.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemBase SASz/OS9.4_M49.4 TS1M4
z/OS 64-bit9.4_M49.4 TS1M4
Microsoft® Windows® for x649.4_M49.4 TS1M4
Microsoft Windows 8 Enterprise 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8 Enterprise x649.4_M49.4 TS1M4
Microsoft Windows 8 Pro 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8 Pro x649.4_M49.4 TS1M4
Microsoft Windows 8.1 Enterprise 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8.1 Enterprise x649.4_M49.4 TS1M4
Microsoft Windows 8.1 Pro 32-bit9.4_M49.4 TS1M4
Microsoft Windows 8.1 Pro x649.4_M49.4 TS1M4
Microsoft Windows 109.4_M49.4 TS1M4
Microsoft Windows Server 20089.4_M49.4 TS1M4
Microsoft Windows Server 2008 R29.4_M49.4 TS1M4
Microsoft Windows Server 2008 for x649.4_M49.4 TS1M4
Microsoft Windows Server 2012 Datacenter9.4_M49.4 TS1M4
Microsoft Windows Server 2012 R2 Datacenter9.4_M49.4 TS1M4
Microsoft Windows Server 2012 R2 Std9.4_M49.4 TS1M4
Microsoft Windows Server 2012 Std9.4_M49.4 TS1M4
Windows 7 Enterprise 32 bit9.4_M49.4 TS1M4
Windows 7 Enterprise x649.4_M49.4 TS1M4
Windows 7 Home Premium 32 bit9.4_M49.4 TS1M4
Windows 7 Home Premium x649.4_M49.4 TS1M4
Windows 7 Professional 32 bit9.4_M49.4 TS1M4
Windows 7 Professional x649.4_M49.4 TS1M4
Windows 7 Ultimate 32 bit9.4_M49.4 TS1M4
Windows 7 Ultimate x649.4_M49.4 TS1M4
64-bit Enabled AIX9.4_M49.4 TS1M4
64-bit Enabled Solaris9.4_M49.4 TS1M4
HP-UX IPF9.4_M49.4 TS1M4
Linux for x649.4_M49.4 TS1M4
Solaris for x649.4_M49.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.