| This post was kindly contributed by Blogging about all things SAS - go there to comment and to read the full post. |
I have been doing some work with a customer who is implementing Business Objects Data Federator as the preferred mechanism for all tools to access their corporate data.
This includes accessing data in their corporate applications as well as the Data Warehouse.
They have a SAS Analytics environment and would like SAS to comply with this standard by accessing data in SAS via the Data Federator rather than accessing the data sources directly.
The trick (isnt there always a trick!) is that the BO Data Federator can only be accessed via a JDBC connection.
Of course I thought no problem, SAS can access any data source in the world, can’t it? Well no JDBC seems to be one of the few data sources SAS can not access natively as there is no SAS/Access to JDBC.
We have been testing third party JDBC > ODBC bridges and struck the old SAS/Access for ODBC 64 bit can’t access a 32 bit ODBC driver issue. And of course the JDBC > ODBC bridge we were testing only had a 32 bit provider. We have found a different provider with a 64 bit version we are testing now.
Anyway I sat in a session at Vegas presented by the SAS/Access product manager so I asked him if a SAS/Access to JDBC was in the pipeline.
He said they had received a few requests over the years, but not enough to put it on the priority list.
So if you need a SAS/Access to JDBC engine (like my customer does) then log a tech support track now asking for one, and when can help each other help ourselves.
| This post was kindly contributed by Blogging about all things SAS - go there to comment and to read the full post. |