06-13-2014 04:04 AM
Review all settings specific for sas/access netezza.
The shared read only should help a lot. The Libname options must be carefully set think also on SQL trace settings.
The eguide SQL query builder looks fine with sas datasets. With external dbms systems there are lot of bad behavior I als.
The SQL Pass trough setting is working but not tailored to all native sql dialects. Enough pitfalls...
07-09-2014 02:23 AM
I am sorry to disagree gxmessier. That kind of an answer is well known to be common to gain time, often with no fix at all.
Of you have got this answer from somebody you are not taken seriously.
If is about connect errors, That is part of SAS/ACCESS® Interface to Netezza. Saskiwi link is having mentioned that.
Eguide query builder is even having more problems.
Either is must use implicit SQL pass thru trusting the ANSI SQL translating to native SQL lingo's or it must do solving the native SQL lingo's in a explicit pass thru.
This problem is a very challenging once knowing how all those SQL lingo's are different. For the moment you can expect the most easy SQL's will work but as soon something more as trivial is done some weird bad behavior can occur. As SAS is rather old it can be even caused by once smart approached built in that in this newer versions are causing problems (cursor management into to DBMS).