To add a library in
SAS Enterprise Guide Explorer, select
FileNew Library and follow the
prompts on each page of the Library Wizard. Use the following information
as a guide, because the pages and options that you see will depend
on your situation.
On page 1 of the Library
Wizard, the eight-character library name must be unique on that server.
The library name is entered in uppercase letters.
On page 2 of the wizard,
you assign the library using one of the following:
specifies that SAS
Enterprise Guide uses the metadata that is supplied in the wizard
to assign the library, using the native engine. No table or column
metadata is used.
specifies that the
library is assigned in an AUTOEXEC statement or through the METAAUTOINIT
system option. SAS Enterprise Guide does not use the metadata that
you specify for the library, but assumes that the library is already
assigned.
specifies that SAS
Enterprise Guide assigns the library by using the META engine.
If
Show
only tables with metadata definitions is selected, then
only tables that have metadata definitions appear when the library
is selected. When this option is selected, the library is always Read-Only.
This option is equivalent to the default behavior of the META engine.
If the library is assigned using the metadata LIBNAME engine and this
option is selected, it is equivalent to the METAOUT=ALL option.
If the check box is
not selected, then all tables in the library will appear. Tables appear
even if you deny ReadMetadata permission or if the table is not registered
in the metadata repository. Permissions are enforced if a user tries
to open a restricted table. In this mode, the library is not Read-Only.
This option is equivalent to the METAOUT=DATA option.
If
Allow
tables to be created and deleted is selected, then you
can read, update, create, and delete tables. You can also insert records,
create columns, and change column properties in tables. A newly created
table must be registered in metadata before it can be read.
On page 4 of the wizard,
you specify the engine type for the library (file system, database
system, or WebDAV) and specific information for the engine type that
you select. If you are defining a file system or database system library,
you must choose an engine. Select the SAS engine with which the data
was created. For more information about engines, see the SAS documentation
for your operating environment. See also the chapter that corresponds
to your database management system in
SAS/ACCESS for Relational
Databases: Reference.
Also, on page 4 of the
wizard, you might be asked to specify the physical path where the
library resides on the server. Depending on the value of the
Engine
Type field,
Path might not be
present. You can use the following wildcards to substitute values
into the specified path:
substitutes the Windows
user ID. For example, using the Windows user ID ebeacon,
the literal Path value in the wizard is \\librarypath\<userid> and
the actual path is\\librarypath\ebeacon.
substitutes the SAS
Enterprise Guide sample directory. For example, <sample>\data can
become C:\Program Files\SAS\Enterprise Guide 5.1\Sample\data.
substitutes the server
logon user ID.
substitutes the server
password.
substitutes the library
logon user ID.
substitutes the library
logon password.
Note: The libraries that you create
with these wildcard substitutions can fail to provide access to those
libraries for client applications other than SAS Enterprise Guide
and the SAS Add-In for Microsoft Office.
On page 5 of the wizard,
you can specify library options and values. If wildcards are valid
in the
Path field, then you can also use
them in the
Options field. Avoid using prompting
options such as DBPROMPT=YES. For additional options, see the chapter
that corresponds to your database management system in
SAS/ACCESS
for Relational Databases: Reference.
On page 6 of the wizard,
select the folder to which the library belongs. If you do not select
a folder, the library is automatically stored in the
Shared
Data
folder.
On page 7, test the
library definition. If the library name or libref is not unique on
all servers, the conflict is listed in the
Status column.
After you complete the
wizard, the library is created and then displayed in the viewer under
the client libraries for the specified servers.