| ActiveX Data Objects (ADO) | a simplified programming interface to OLE DB. Both ADO and OLE DB have been developed by Microsoft. |
| ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX) | an extension to the ADO programming interface that enables users to create, modify, and delete database objects such as tables. ADOX can also be used to manage user permissions and group permissions on database objects. ADOX was developed by Microsoft. |
| ActiveX Data Objects—Multidimensional (ADO MD) | an extension to the ADO programming interface that enables users to read multidimensional schema, to query cubes, and to retrieve the results. ADO MD accesses data through a multidimensional data provider such as the IOM Data Provider. ADO MD was developed by Microsoft. |
| cube | a logical set of data that is organized and structured in a hierarchical, multidimensional arrangement. A cube is a directory structure, not a single file. A cube can include measures, and it can have numerous dimensions and levels of data. |
| Component Object Model (COM) | a specification for developing objects that has been defined by Microsoft. COM is a language-neutral binary interface specification for Windows objects and a set of run-time functions for instantiating them. With COM, it is possible to build an object using one language, and use that object in another language. Both Object Linking and Embedding (OLE) and ActiveX were developed using COM. |
| consumer | an application that uses the ADO or OLE DB specification to request functionality or data from a data provider through OLE DB interfaces. A typical ADO consumer might submit a query to a data provider and then display the results of that query. |
| data provider | software that makes data available through the OLE DB interfaces to a consumer such as an ADO or ADO MD application. |
| Integrated Object Model (IOM) | the set of object-based interfaces that is surfaced by SAS software when it is run as an object server. |
| Integrated Object Model (IOM) Server | a SAS object server that is launched to fulfill client requests for IOM services. |
| libref | a name that is temporarily associated with a SAS data library. The complete name of a SAS file consists of two words, separated by a period. The libref, which is the first word, indicates the library. The second word is the name of the specific SAS file. For example, in VLIB.NEWBDAY, the libref VLIB tells SAS where to look to find the file NEWBDAY. |
| LDAP (Lightweight Directory Access Protocol) | the protocol that is used by applications to store and retrieve information in a network directory (LDAP server). |
| member-level access | the access to a SAS data library that permits only one user to use a member (such as a SAS data set) at a time. |
| member name | a name that is assigned to a SAS file in a SAS library. A member name can reference a SAS data set, a SAS catalog, a SAS access descriptor, or a stored program. |
| Object Linking and Embedding (OLE) | a method of interprocess communication supported by Windows that involves a client/server architecture. OLE enables an object created by one application to be embedded in or linked to another application. |
| OLE DB | an open specification that has been developed by Microsoft for accessing both relational and nonrelational data. OLE DB interfaces can provide much of the same functionality that is provided by database management systems. OLE DB evolved from the Open Database Connectivity (ODBC) application programming interface. |
| OLE DB for OLAP (ODBO) | an extension to OLE DB that enables users to access multidimensional databases in addition to relational databases. The SAS OLAP Data Provider supports the OLE DB for OLAP interface. |
| Online Analytical Processing (OLAP) | a software technology that enables users to dynamically analyze data that is stored in multidimensional database (MDDB) tables. |
| persisted information | information such as formatting that remains associated with a data source element such as a column even after the program that created or accessed the data has been terminated. Persisted information can be retrieved programmatically at any time. |
| SAS/ACCESS software | a software interface that makes data from an external database management system (DBMS) directly available to SAS and SAS data directly available to a DBMS. Generally, a SAS/ACCESS interface consists of three parts: the ACCESS procedure, which defines descriptor files; the interface view engine, which allows you to use DBMS data in SAS programs in much the same way you would use data stored in SAS data files; and the DBLOAD procedure, which enables you to create and load DBMS tables using data from SAS data files and PROC SQL views. |
| SAS catalog | a SAS file that stores many different kinds of information in smaller units called catalog entries. A single SAS catalog can contain several different types of catalog entries. |
| SAS OLAP Server | a server that provides access to multidimensional data. The data is queried using the multidimensional expression language (MDX). |
| SAS/SHARE Server | an execution of the SERVER procedure. The SERVER procedure is part of SAS/SHARE software. A server runs in a separate SAS execution that services client's SAS sessions by controlling and executing input and output requests to one or more SAS data libraries. The multi-user SAS/SHARE server enables two or more clients to write to the same SAS file (for example, a data set or a catalog) at the same time. |
| SAS Workspace Manager | a component that executes on the client machine and that is used to create and manage SAS workspaces on IOM servers. The Workspace Manager uses IOM server definitions that are administered separately from the application. This enables, for example, a client application to connect to a server simply by using a logical name. The definition for this server can change as required without affecting the application. |
| transport file | a sequential file containing a SAS data library, a SAS catalog, or a SAS data set in transport format as produced by the CPORT procedure or as written by the XPORT engine or the Version 5 XCOPY or COPY procedures. The format of the transport file produced by the CPORT procedure is different from the format of the transport file written by the XPORT engine or the Version 5 COPY or XCOPY procedures; the SAS Data Providers can read files created by the XPORT engine and the Version 5 COPY and XCOPY procedures. You can use transport files to move SAS data libraries, SAS catalogs, and SAS data sets from one operating system or host to another. |
| WHERE processing | a method of conditionally selecting observations for processing in a DATA or PROC step. WHERE processing involves using a WHERE expression in a WHERE statement, a WHERE= data set option, a WHERE clause, or a WHERE command. |
| workspace | a SAS Integrated Object Model (IOM) workspace represents a single session with SAS. It is also a root object in the IOM object hierarchy. |