topic Re: SAS EG Query Builder to Netezza user connection limit issues in SAS Enterprise Guide

SAS EG Query Builder to Netezza user connection limit issues

gxmessier — Thu, 12 Jun 2014 19:49:21 GMT

Any suggestions on this topic as we are limited to 12 connections per user?

Re: SAS EG Query Builder to Netezza user connection limit issues

SASKiwi — Fri, 13 Jun 2014 00:49:55 GMT

Does this help?

http://support.sas.com/kb/49/604.html

Re: SAS EG Query Builder to Netezza user connection limit issues

jakarman — Fri, 13 Jun 2014 08:04:57 GMT

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...

Re: SAS EG Query Builder to Netezza user connection limit issues

gxmessier — Wed, 09 Jul 2014 01:15:10 GMT

Problem with be fixed in EG version 6.1 from what I understand.

Re: SAS EG Query Builder to Netezza user connection limit issues

jakarman — Wed, 09 Jul 2014 06:23:52 GMT

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).