You are on page 1of 5

What is SAS/access interface?

SAS/ACCESS software provides an interface between the SAS System and relational database management systems (DBMSs). This highly optimized data access engine enables SAS solutions to read, write and update data regardless of the data source or platform. How do you configure SAS/ACCESS interface to Teradata? To Configure SAS/ACCESS interface to Teradata, I will add the location of the shared libraries to one of the system environment variables. If it is an AIX system, I will export the path either to the SASROOT! or .profile using $ LIBPATH=TERADATA-CLIENT-LOCATION:$LIBPATH $ export LIBPATH If it is a Solaris system, I will export the path using $ LD_LIBRARY_PATH=TERADATA-CLIENT-LOCATION:$LD_LIBRARY_PATH $ export LD_LIBRARY_PATH Then I will run the makefile script to complete the installation of SAS/ACCESS Interface to Teradata in AIX. This makefile will link the Teradata CLI client libraries, and creates the "sastra" image in !SASROOT/sasexe. (To do this I will: Make the !SASROOT/misc/dbi directory the current directory. Execute make -f sastra.mak. This creates the "sastra" image in the !SASROOT/sasexe directory.) To add the new database I will add a new TNS entry in /etc/hosts To connect to the corresponding database I will write the corresponding LIBname statement How do you configure SAS/ACCESS interface to Oracle? To Configure SAS/access interface to Oracle, I will export the ORACLE_HOME path to the environment variable. I will point the shared library path variable to the path where Oracle shared libraries are located. If it is an AIX system, I will export the path either to the SASROOT! or .profile using $ LIBPATH=$ORACLE_HOME/lib:$LIBPATH $ export LIBPATH

If it is a Solaris system, I will export the path using $ LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH $ export LD_LIBRARY_PATH To add the new database I will add a new TNS entry in TNSNames.ora file which will be in the path $ORACLE_HOME/NETWORK/ADMIN directory How do you know that SAS Access Interface to Oracle/ Teradata works is installed in your system? I can see what all applications are installed in SAS Server in the path !SASROOT/SASSETUP, if I see a file with filename SASORA and SASTRA in the SASEXE then the SAS/Access interface to oracle and Teradata are installed in the SAS Server. Speak about the Hardware Information in the current site: We have 2 Quad core Xeon Processors with 2.33 GHz; we are operating in Solaris 5.10 x86 on HP BL 460C Server with 50 Terabytes of SAN attached to it and 128GB RAM. Details on SAS Installation Procedures done in the past We had just one Solaris server on which I have to deploy SAS, so I used Full prompt mode to install SAS on the server with EBI Three machine default plan file. And I know SAS can be installed in two other modes (Quiet mode and Partial Prompt) with the help of Response file, but I just used Full Prompt mode to deploy SAS into our server. Details on SAS Migration Procedures done in the past I migrated SAS 9.1.3 on AIX to SAS 9.2 on Solaris Server. As a part of migration I migrated all the SAS 9.1.3 Metadata, migrated all User Datasets and Code, (we have around 100+ jobs that are running on Control-M so I migrated all the production jobs) and jobs scheduled in crontab. As well as, I coordinated with our UNIX system administrator to create all the users and groups on the new SAS 9.2 Solaris server. Using the SMU (SAS Migration Utility) I created a migration package on SAS 9.1.3 Server, copied the migration package to SAS 9.2 Server and pointed to the migration package while installing SAS 9.2 on the new Solaris server. While Migrating Metadata I migrated -- all the libraries and tables information that is registered in Metadata, all the User Metadata containing user identifications and groups, all the access control templates, all database server information that is registered in metadata, the metadata associated with stored processes and Enterprise Miner projects.

I installed and configured the SAS/Access interface engine for DB2, Oracle, and teradata on the new SAS 9.2 Solaris environment, to be able to access these databases. I created the pre-defined SAS Metadata Libraries pointing to (Oracle, DB2, Teradata) databases and imported the data tables to these libraries. I also migrated all Enterprise Guide Projects from 4.0 to 4.3 and migrated all Enterprise Miner Projects from 5.3 to 6.1. Post installation Steps after migration?

What are access control templates? Access control templates allow you to reuse the permissions which are once set using them. ACTs are used to avoid having to repeatedly set the same explicit permissions for the same identities on multiple items. When you apply an ACT to an item, the ACT settings are added to the item's protections. Speak about Performance Tuning and Optimization of the server Modifying a system in such a way that increases the scalability of the system is called performance tuning. In Performance tuning I will identify the part of the system that is critical for improving the performance i.e. part of the system which is having high system load making it slow or unresponsive and thereby reaching its bottleneck. To identify which part of the system is facing bottleneck problems I used some monitoring tools to monitor the server activities with the parameters like CPU usage, Memory Usage, Processing time, etc.. To optimize system performance and maximize productivity, UNIX performance and resource usage should be monitored. To optimize the system performance we can use load balancing, caching strategy, etc., To achieve efficient load balancing, I will divide the jobs which can run during off peak hours so that some batch jobs will run on weekends when the load on the server is low. Default Port Numbers for SAS Servers and Spawners:
Default Port Value 8561 8581 8801 8811 8821 Description SAS Metadata Server port SAS object spawner: operator port SAS object spawner: pooled workspace server port bank 1 SAS object spawner: pooled workspace server port bank 2 SAS object spawner: pooled workspace server port bank 3

8591* 8591 8701 8601 8611 8621 8631 5451 8551 7551 2171 5091 8451 10021 same time.
*

SAS Workspace Server port Metadata utilities SAS Workspace Server port SAS Pooled Workspace Server port SAS Stored Process Server: bridge connection SAS Stored Process Server: load balancing connection 1 (MultiBridge) SAS Stored Process Server: load balancing connection 2 (MultiBridge) SAS Stored Process Server: load balancing connection 3 (MultiBridge) SAS OLAP Server port SAS/SHARE server port SAS/CONNECT server port SAS Table Server port SAS Remote Services application port Operating System Services scheduler port SAS Deployment Tester server port

* In SAS 9.2, two or more workspace servers can share the same port even if they are running at the

SAS Add in for Microsoft office:

Do you have any idea and EBI security how do impose security in metadata SAS Enterprise Miner troubleshooting Any SAS issues in the current site May be little bit about scripting and automation Cleaning and purge criteria of SAS Data Inclination towards SAS GRID and other interesting stuff.. --

/usr /etc /opt !SASROOT/sassetup -- run option view all the application installed !SASROOT/sasexe/sasora, sastra, sasdbu -- file unte installed .. Configure SAS /Acces interface to Oracle

1) You need to export the paths for ORACLE_HOME , TERADATA_HOME ,DB2HOME 2) ORACLE_HOME/network/admin/tnsnames.ora -- this file will contain all the databases Libname mani Oracle datasrc=dev01 schema= user= password= tnsnames.ora -tnsnames of a database Libname mani teradata server=dev01 schema= user= password= /etc/hosts Libname mani db2 database=dev01 schema= user= password= db2 profile -- db2 admin Libname mani ODBC datasrc=dev01 schema= user= password= odbc.ini - odbc entries AIX --- /etc/profile Solaris -- /etc/skel/profile

LIBPATH ORACLE_HOME SASROOT!/sasenv_local -- env file for SAS

5 ROM -- SUN Sparc 10 OS

You might also like