11-25-2015 01:18 AM
1. In 2014 we used a Base SAS92 program running on a WindowsXP PC to use a local Adabas ODBC driver to read Adabas D tables (version 15.01.07.21) on a Windows server. It ran cleanly and efficiently.
2. In 2015 we used a Base SAS94 program running on a Red Hat Linux6.5 machine to use an Adabas ODBC driver to read Adabas D tables (version 15.01.07.21) on a Windows server. It ran very inefficiently: the unwanted Adabas D database utility "updatestatistics" was executed for every one of the 59 Adabas D tables. The Adabas ODBC driver resides on our SAS PC File Server Windows 2008 r2sp1 machine.
3. The technically advanced SoftwareAG group in Europe state that it is not an Adabas D problem. It is a SAS problem. Something has changed in the way the SAS program connects to, or interrogates, the Adabas D database.
4. We have tried many different investigations including checking DSN related SQL trace logs. We cannot find any reason for SAS94 to trigger the "updatestatistics" executable. Any ideas gratefully received. 25.11.2015.
11-25-2015 01:46 AM
Please provide Suspect A - the SAS program that was alleged to commit this heinous crime. Does the updatestatistics get triggered for all queries or just some? Are you using an SQL PASSTHRU query? If not I would try PASSTHRU - same problem?
How about installing SAS 9.4 on a PC, configured exactly like your SAS 9.2 setup. If it works exactly like SAS 9.2 then it can't be SAS 9.4 causing the problem, it must be something else.