Thanks all for you comments.  After our servers were rebooted last night, none of these files were cleaned up as suspected.  I will have to create a script to clean them up myself then. ... View more

Thanks for responses to date.  I was curious about the Flitcon tools but alas, the VA firewall had that identified as a black-listed site so there is little hope of getting anyone from our Technical Reference Modeling office to perform a software review on that other toolkit.   I did browse thru that site on my home computer but didn't see anything leading me to believe it approached the capabilities offered by the current Metacoda tools.  I shall take these findings back to our Acquistions office and hope for the best. ... View more

HI @AndrewHowell   Yep we do have some team LASR servers, but it's the same problem - it would the impact more than one person that is connected to that LASR.  Although the impact would be less than if they were running it on the public LASR. ... View more

So you will have 2 metadata servers?   If so, do both developers have metadata identities in both environments? I am asking these questions because I am wondering if seting up a SAS Folder and assigning groups with certain permissions might help the situation.   The problem is not really the pre-assignment but the fact that 2 people need to access the same table at the same time. Is that a fair statement? ... View more

Tammy, it makes sense to have one metadata server serving the VA work the BI classic one and the data-mining.That brings you at the same level of an AD security administration with Windows and RBAC. The VA work (end users) are accessed by lasr-servers. You can define many of those. The simple bi work for less advanced users you can organize by SAS APP users on some compute servers. Putting that data and users  there. You can define many SAS APP servers as they are meant as applications data and code by SAS. Those data miners can have their own SAS APP servers on dedicated compute servers. By that segregation you are needing groups to assign the users to all of these data segregated appservers. This approach is quite common. There is a problem with special roles like a person doing bi work and administration. In that case a dual account is normally mandatory. That solves also the part of data administration with VA. Windows  admins are using that approach theirself but seeing SAS as something like excel do not make the association to do it similar with SAS. I am wondering how you would go on to protect system resource usage and data security by trying to prohibit excel. ... View more

Tammy that environment is like a natural wilderness.  ;<))     To get it more social organized according an ICT habitat you have to start. One of the things I would advice to do is do a quick check whether you are needing additional appservers. The appservers are what the name is indicating a segregation in application areas/domains. Having that well planned and ordered all things after that are more easy to implement and migrate. Libnames can be defines as autoexexs (usermods on the appserver) and as metadata definitions they have the goal of eliminating those from user code. The autoexec approach is behaving more direct in the same way as the normal SAS code. Putting all in SAS metadata is building additional layers around those. Having those pathnames hardcode in source "why not it works" is a bad approach for conversions and release management as the same for developing in production "who changed that?". ... View more

Thanks so much Sanjay, and yes I'm using v9.4.  I've been reading some of your white papers and blogs as well which have been very useful in understanding the SG procedures. ... View more