Creating a SAS Software Depot

Best Practices for SAS Software Depots

For customers who download SAS, their SAS Software Depot is the only copy of their SAS order. The depot contains the files from which SAS is initially installed. For this reason, it is important to use these best practices when managing your depot:

Keep your depot.

When you keep your SAS 9.2 depot, applying maintenance and upgrades becomes easier because you only need to download the changed depot files instead of having to download an entire SAS order.
Perform routine backups.

As with your SAS production system, it is important to routinely back up your SAS Software Depot and verify the integrity of these backups.

Note: Another important reason for securing and backing up your SAS Software Depot is that there are limits on the number of times that you can download your order from SAS.
Secure the depot location.

Problems such as data loss, virus infection, and file corruption can compromise your investment in SAS. It is thus imperative that you have a comprehensive security policy in place to protect your depot.
Store SAS installation data files with your depot.

The SAS installation data file for your orders contains information that is integral to successfully deploying SAS. As you get these data files from SAS--such as the file that contains your permanent SAS license key--it is important that you store them with your depot in the sid_files directory.

CAUTION:
If you do not use the installation data file that supports the products you are planning to install and configure on this machine, you might experience errors later when you are trying to use the products.
Create a depot administrator.

Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. Separating depot administration from routine depot usage is a best practice that will further protect your SAS Software Depot.

Top of Page