Organizing SAS Libraries

[StephenOverton]

Anybody have any thoughts on how to organize SAS libraries??

I'm debating on whether or not I should have more libraries grouping by functional area of analysis rather than source database. Thoughts on best practices?

[StephenOverton]

Here is a more clear example:

Right now lets say I have a few source systems: A, B, and C

I basically have 2 libraries for each source system, one for the source tables themselves and another to store data about the source data (summary data, dimensional data, etc).

[Peter_C]

why more than one?
1 access restrictions
2 storage requirements (criteria like small&fast=ssd, large&indexed=spde)
3 personal versus shared
4 sas/access engine

for me, fewer is better, but rules 1 and 4 seem most important.

your business rules are most important

PeterC

[sbb]

Backup retention and frequency for recovery is another consideration, if the data-store is going to be large, and depending on how often the SAS code/objects are updated/replaced/changed, again for recovery considerations. The relative importance of each type of data being stored will also help determine how it is to be organized. In an enterprise environment, there may be audit requirements that influence your approach and organization structure.

Scott Barry
SBBWorks, Inc.

[StephenOverton]

From Peter's list:
1) Mostly everything in my company will be open to the public, we are small.
2) I like this concept, I'll think about it further, thanks
3) Again, we are small so personal/shared libraries wont matter

[Peter_C]

(1) + (3) perhaps this creates a problem
I think open access is incompatable with read/update/create unless you have something like sas/share