Postgres is not Oracle. I recently did just what you are suggesting for a product wanting a later version of Postgres than we distribute. In general, there was no real difference between setting up for the external server than for an "internal" server. We had to decide to use the same JDBC jar as we use for the internal installations in order to prevent conflicts since tcServer puts each referenced jar in the same directory for actual use. The additional metadata from what I've already called out is to setup a Server Component in the Server Manager plugin to hook your SAS Client Connection to. In fact, I believe you wind up creating both at once. One caveat on client software, we didn't really use any during configurations or migrations because we expect the user to see to managing third party databases. You may want to copy the client scripts from your Postgres server machine to the SAS machine. ... View more

@Yaswantha001, Since you have the Web Infrastructure platform installed, you should also have SASWebInfrastructureDataBaseJDBCDrivers and SASWebInfrastructurePlatformDataServer. I believe they contain all that you need. If manually standing up a PostgreSQL server is not your cup of tea, then you can use the client software, especially pgAdmin3.exe to add a database and login. Once done, you can use SAS Management Console to setup your metadata. You need to add a SAS Client Connection for your database to the existing server and then create SAS Library metadata to read and write through. Of course you must have installed SAS/ACCESS to Postgres. SAS MC has some very good help pages. A couple of tips for the Library: a) in the advanced options Output tab, set "Preserve column names as in the DBMS to 'No'; b) on the Input/Output tab set  Preserve DBMS table names to 'No'; c) the Database Schema Name is generally 'public'.   To setup access to the database, the easy path is to create a database user group in SAS MC. Add a login Account) to that group using the same Authentication Domain as in your SAS Client Connection. Add the name of the login you created for the database and the password. Make the SAS Administrators group as a member of  your group for metadata access. Add any other external users as defined in metadata as member if they need to have access to the data.   One last bit is that you can right click on your library in the Data Library Manager plug in for SAS MC and have it display the libname statement you need to connect to your database. Quite handy.   This is absolutely the short course. Check with SAS Technical Support for any documentation you can access that may help you with this. ... View more

We need the IT_*_install.log from :\Users\ \AppData\Local\SAS\SASDeploymentWizard. ... View more

We never got a reply or the logs. If you can supply the logs I can elevate it to the developers. Note: Check your System Requirements and make sure Windows 10 is a supported environment. ... View more

I'm working with the guys who write and maintain the SAS Deployment Wizard code. They stress that they need an IT.log that covers a period when the error occured to proceed. ... View more

In the SDW.log the one thing that jumps out at me is: WARNUNG: The current user (FFG-NBDE-012\xxx) is not the same user that last installed to this SAS Home location: FFG-NBDE-012\Admin Are you certain that you have full-control over SASHome and Config directories? ... View more

The IT log only shows January 3rd. Is that correct? ... View more

I've pinged some others. The IT.log should also be of interest regarding installation failures. As for the missing jars, you'd think it would install them. Note that you can attach the logs so that I can share them. ... View more

Note that your user directory (C:\Users\yourID) there is a hidden AppData directory. Open AppData\Local\SAS\SASDeploymentWizard. There are a number of logs. I suggest starting with the SDW.log concurrent with your upgrade installation attempt. ... View more

After selecting Next, the sualog should change and show the SAS Deployment loading the installation package for the product being upgraded and then shows  it checking to make sure it can write to files being update. If the ODBC driver is in use you should see the of files that it cannot update. Have you stopped all SAS jobs and services? Are you seeing this system check dialog? ... View more

I don't know which products you have licensed. If SAS  Web Infrastructure Platform is the only product using an instance of SAS Web Infrastructure Platform Data Server, as you describe, it may not come with SAS/ACCESS to PostgreSQL. I believe that product accesses its data via direct JDBC. I would have to check the packaging overview for any specific product to see if it comes with ACCESS to PostgreSQL The SAS Solutions that I've been working with do to support DBMS access using SAS Libraries. The SAS/ACCESSS license may have a usage restriction for use with that product only. Tech Support can probably help you interpret your licensing structure. ... View more

As a configuration developer for SAS, I've seen less and less ODBC and more SAS/ACCESS. These days, our 9.4 based solutions use SAS/ACCESS to PostgreSQL extensively. It is an excellent product and I personally recommend it. However, if price is your driver, ODBC is more generic. ... View more