Netezza native connectivity and DS ID access type
Posted: Thu Nov 22, 2012 6:50 am
I am trying to understand Netezza connectivity, and type of access between Datastage to Netezza, and hoping someone can help. Some of these questions may be basic but would surely help my undrestanding on the topic.
I know Netezza native connectivity is available since 8.1 version and 8.7 makes it that much better but have following questions:
1) When I look at the Netezza driver used in DS, its located at following path and has ODBC reference in the naming. If it is a native driver, why does it use ODBC naming for ".so" file?
Location of the driver and its name: /netezza/lib/libnzsqlodbc3_64bit.so
2) How do we ensure we have Native connectivity to Netezza via Datastage?
3) Does use of Netezza Connector OR Netezza Enterprise sage mean native connectivity? (or dumb quesiton can these stages also be connected via ODBC)?
4) What kind of access rights does Datastage batch id/user id suppose to have in Netezza database, as I understand even with Netezza Connector, User ID could still create Work tables etc.
I know Netezza native connectivity is available since 8.1 version and 8.7 makes it that much better but have following questions:
1) When I look at the Netezza driver used in DS, its located at following path and has ODBC reference in the naming. If it is a native driver, why does it use ODBC naming for ".so" file?
Location of the driver and its name: /netezza/lib/libnzsqlodbc3_64bit.so
2) How do we ensure we have Native connectivity to Netezza via Datastage?
3) Does use of Netezza Connector OR Netezza Enterprise sage mean native connectivity? (or dumb quesiton can these stages also be connected via ODBC)?
4) What kind of access rights does Datastage batch id/user id suppose to have in Netezza database, as I understand even with Netezza Connector, User ID could still create Work tables etc.