Creating, Registering, Moving, Copying, Renaming, and Deleting SAS Metadata Repositories

About SAS Metadata Repositories

A metadata repository is a physical location in which a collection of related metadata objects is stored. Metadata repositories are managed by a repository manager, which is a library of tables that define the set of repositories that can be accessed by a SAS Metadata Server. A metadata server cannot be started without a repository manager. Each metadata server can have only one repository manager.

The SAS Metadata Server supports three types of metadata repositories:

Foundation repositories

are the required metadata stores for SAS Metadata Servers. Each metadata server has one foundation repository that is created by default when the metadata server is configured. The default name of the foundation repository is Foundation. (If you performed a custom installation, then you might have assigned a different name.) You cannot create more than one foundation repository.

Custom repositories

are optional metadata stores for SAS Metadata Servers that can be configured in addition to the foundation repository. Custom repositories are useful for physically segregating metadata for storage or security purposes.

For example:

If your metadata storage requirements exceed the capacity of a single metadata storage location, you could create custom repositories on separate storage devices that are accessible to the metadata server.
If you have metadata that is highly sensitive, you could create a custom repository for that metadata and store it in a directory that has an exceptionally high level of protection from unauthorized access.

Custom repositories appear as separate folders in the Folders view of SAS Management Console and in other client applications.

To create a custom repository, see Create a Custom Repository.

Project repositories

are metadata repositories that serve as isolated work areas or playpens. Project repositories are available for SAS Data Integration Studio only. In general, each user who participates in change management has his or her own project repository.

A project repository enables a user to check out and lock metadata from a foundation repository or a custom repository so that the metadata can be modified and tested in a separate area. When the metadata is ready, it is checked in and unlocked so that it is available to other users.

For information about creating project repositories, see Setting Up Change Management in the SAS Intelligence Platform: Desktop Application Administration Guide.

The SAS Deployment Wizard creates just one repository, which is the foundation repository. If you create additional repositories, then the metadata in a given repository can be associated with metadata in other repositories as follows:

Metadata in a custom repository can be associated with metadata in the foundation repository and with metadata in all other custom repositories.
Metadata in the foundation repository or in any custom repository can be checked out to any project repository, as long as the user has the appropriate permissions.
Metadata that is checked out to a project repository can be associated with metadata in the foundation repository or with metadata in any custom repository (but not with metadata that is checked out to a different project repository).

Note:

In SAS 9.2, it is not necessary to define dependencies between repositories. If a repository dependency was defined in SAS 9.1.3, then the dependency relationship is eliminated during the SAS 9.1.3 to SAS 9.2 migration process. However, the existing associations between metadata objects still remain in effect
Effective with the November 2010 release, an additional repository called BILineage is created automatically the first time an unrestricted administrative user logs on to SAS Management Console. This repository stores metadata lineage and impact analysis data that is generated by SAS Data Integration Studio, SAS OLAP Cube Studio, and the BI Lineage plug-in for SAS Management Console. The BILineage repository should not be used for any other purpose. For more information, see Using the BI Lineage Plug-in.

Top of Page