Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Entity–attribute–value model wikipedia , lookup
Microsoft Access wikipedia , lookup
Clusterpoint wikipedia , lookup
Data vault modeling wikipedia , lookup
Information privacy law wikipedia , lookup
Business intelligence wikipedia , lookup
Open data in the United Kingdom wikipedia , lookup
Infyoclvc,..tron to SAS/Ac,a,SS® Introduction SAS/ACCESS software is a powerful tool in today's relational processing environments. Many companies around the world use SAS software as their tool of choice to extract information from an existing relational database. SAS Institute has created many versions of the SAS/ACCESS product to fluently communicate with popular database management systems found in these companies. This presentation discusses the use of SAS/ACCESS as a fundamental tool with today's relational databases. It is intended for users new to SAS/ACCESS software. Multiple Engine Architecture In SAS Using relational databases and external file formats in a SAS program Is simple. It is just like referring to a SAS data set, however, the data comes from the relational database, instead offrom within SAS. e This is called Multiple Engine Architecture. It can provide for direct access to data without the need for copying into SAS, transparent access to the data, and database access without major physical storage requirements. SYSTEM2000 (MVS, CMS) SQUDS (CMS, VSE) ORACLE (VMS, PRIMOS, AOSNS. AIX.· SunOS. HP-UX) Database Manager (OS/2) dBASE .DBF file (OS/2. Windows) Lotus 123 .DIF file (OSI2. Windows) Prime Information (PRIMOS) ASI400 (OS/2. Windows) VSAM (MVS) SYBASE (SunOS.VMS) CAlIDMS (MVS) Others Interface, ACCESS, OSLOAO The diagram below outlines the relationship between the SAS environment and the relational database environment. The SAS/ACCESS software consists of: Interface Engine Field names, formats, and types are transparent between different environments This is the part that transfers data to the relational database and the SAS system. It provides transparent read and write abilities. ACCESS Procedure A Utility for defining ACCESS and VIEW descriptors that read and write information with relational databases. The two types of engines available with SAS are: "Native" SoftwaYG- engines that read and write SAS data views, SAS data sets, and SAS transport files. The current native engines are: DB lOAD Procedure Used to create new tables. insert data. and to pass administrative Sal information to the DBMS. SPSS OSIRIS Data Reading, Updating and Appending BMDP Data reading. updating and appending can be done with the procedures below. DEC Common Data Dictionary (CDD) DEC Digital Table Interchange Format (DTIF) proc fsview data=view.one "Interface" engines communicate with external environments such as relational databases. The current and. future engines are: proc fsedit data=view.one DB2 (MVS) CA·DATACOM/DB (MVS) RdbNMS (VMS) INGRES (VMS,SunOS) IMS·DUI (MVS) ADABAS (MVS) proc append base=view.one data=view.twoj 31 VIEW Descriptors proc sqlj ACCESS and VIEW Descriptors VIEW deSCriptors are SAS files with a member type of VIEW. They pOint to information stored in ACCESS descriptors and can specify a subset of the columns specified in an ACCESS descriptor. They can define different SAS variable names and formats than what is prescribed in the ACCESS descriptor. View descriptors are referenced as if they were a SAS data set and can specify the order which the information will be retrieved via indexing. When VIEW descriptors are referenced in a SAS program, information comes directly from the DBMS table. No intermediate files are created. DBMS tables are given alias names that are used like SAS Data sets. For example, SQL Pass-Through Facility update view.one set ••• , delete from view. one where ... , insert into view.one values •.• j data view.onej modify view. one j SOl®. created by Dr. Codd of IBM is modeled by PROC SOL. PROC SOL. found in Base. SAS, provides an altemate way to pass statements to the DBMS. You can connect to a DBMS(s) and disconnect from it, pass an SOL SELECT query that can be stored in a SAS data view, and can execute SOL statements available to the DBMS. proc sort data=view.one out=twOj VIEW.ONE is the name of the view descriptor, which is the alias name that relates to the relational database. This view descriptor specifies what data to retrieve from the DBMS table and how to retrieve it. To use a view, simply precede the name of the information with a high level qualifier of what the library name or LlBNAME is. In the above example, it is VIEW. Ntm-: A: So\? dm <;e.t ~ ar.r.,. of the. ~ - . c.;mrl- ~t e Nott:-: SA:S/ACa-SS f"!ldvcA~ hive:. nmikd ~rt the. PROC.. Sd(L.. p~-~ 'f'~rrl1t. ~ the. SA:S/ACa-SS few' 'fW' ~ Pf3MS. ~ of .. the. r When to use the SQL Pass-Through Facility A view descriptor relates to the specification of a DBMS table called an access deSCriptor. PROC ACCESS is used to create view and access descriptors. PROC DBlOAD creates only access descriptors. ACCESS Descriptors ACCESS descriptors are SAS files with a member type of ACCESS. They specify the columns available to SAS in a DBMS table and how information is accessed. ACCESS descriptors contain conversion information for relating DBMS names to SAS variables, types, and formats. They are usually used to create VIEW descriptors. • Joins with large tables from the same DBMS. • SAS/AF applications doing transaction processing _ against a DBMS. _ • When subsetting columns of a VIEW descriptor. • When performing summaries of information (COUNT, AVG, etc... ) DBMS table The relation of SAS to SOL to standard Data Processing is simple: SAS Sal Data Processing SAS Data Set Observation Variable Table Row Column File Record Field ACCESS Procedure PROC ACCESS is available for creating ACCESS and VIEW descriptors, editing and browsing existing descriptors. and reading information from DBMS tables into SAS. ACCESS and . VIEW descriptors can be created online, with program statements in batch, or interactive mode. The DBMS is queried by the SAS system when an ACCESS descriptor is created and a VIEW deSCriptor is used, but not when a VIEW descriptor is created. 32