Hi Richard,

Thanks for the tip. I agree with your "principle of conservation of annoyances". The savings from dropping SAS /ACCESS would not be very good.

What I am more interested in, is how much do you think we would save by dropping SAS/IntrNet?

Don't get me wrong- I like SAS 8.2 - but I'm only asking cause we need to make some budget decisions. Having our SAS rep. come down here and get in negotiations before we know what options are available is not going to help us either.

Kent

"Richard A. DeVenezia" <radevenz@ix.netcom.com> wrote in message news:<2l2c8kF7k5csU1@uni-berlin.de>... > Kent Lewandowski wrote: > > Hello, > > > > I was wondering if any of you experienced SAS users could help. My > > small clin. software company is in the process of reviewing their SAS > > license, i.e. finding a cheaper solution than the constellation we are > > currently using: > > > > SAS / ACCESS + SAS / Share + SAS / Connect + SAS / IntrNet > > > > Our SAS server is currently handling some (not all) reporting duties > > for the main J2EE-type application that has a back-end DB2 database. > > We are using SAS/ACCESS to copy our db2 tables and then performing > > roll-ups / summaries and proc means in batch at night. SAS then > > delivers tabulated reports and graphics in real-time using SAS/IntrNet > > / Integrated Object Module. We don't really want to throw out our SAS > > libraries and code (it after consists of over 5 man-years of labor!) > > so we are considering what different options we have: > > > > - use a SAS/SHARE driver for JDBC (see information below)? in this > > scenario we access our SAS server (read-only) from a connected > > application server and run queries against the SAS tables. We still > > would require the SAS/ACCESS to copy db2 and then perform the nightly > > batch in SAS. Would we save $$$ over our current configuration, in > > your opinion? > > > > - use SAS/SHARE driver for ODBC? > > - other solution? > > > > p.s. in case you were wondering, yes this situation is a result of > > budget constraints! And yes it looks like I will not be here too much > > longer :-) > > > > Appreciate your help- > > > > Kent Lewandowski > > > > -------- > > Requirements for the SAS/SHARE® Driver for JDBC > > The SAS/SHARE driver for JDBC is fully compliant with the JDBC 2.0 > > API. It implements the basic 2.0 Core functionality but does not > > implement the advanced 2.0 Core features of scrollability, batch > > update, and programmatic update. Before you can write and deploy > > programs using the classes that are provided with the SAS/SHARE driver > > for JDBC, your intranet must meet the following requirements: > > Your Java environment supports JDK 1.4.1. Note: An earlier version of > > the JDK might work but is not supported by SAS. > > Your SAS server is running SAS, Version 6 or later. SAS/SHARE software > > is installed as part of your SAS server. > > Your Web server runs on the same machine as your SAS server or has > > network access to the machine running your SAS server. > > If you have a DB2 programmer *and* DB2 has the ability to utilize JDBC, then > you could have a DB2 process *push* the data into SAS tables (via JDBC and > SAS/Share) instead of pulling the data from DB2 via SAS/ACCESS, thus being > able to drop SAS/ACCESS from your package. > > (According to the principle of conservation of annoyances, the savings in > dollars will be lost in the losing of time :) It might take alot longer to > push into SAS than to pull from DB2. You will have to do some benchmarking > to determine if push is viable and time appropriate.