Hello,   I presume (wrongly, perhaps ?) that you want to enable a quota of  number of sessions per user : 2 ongoing sessions maximum per each user. Presently you have no quota and each user can launch as many sessions as he likes, which is the defaut behaviour of as SAS 9 platform with SAS Enterprise Guide (or Add-In, or SAS Studio).   A former colleague once tipped me about how to implement such a rule, it involves a modification of the kind of Metadata server object you have. I cannot remember if I have ever tested this trick so this remains to be thoroughly tested. It might not work at all.   If you don't have a strong knowledge (or the impulse to aquire one) of SAS Metadata then it's going to be difficult somehow.   Here are the main ingredients to make the cake, this list is not comprehensive :   1. Convert your standard Logical Workspace Server to a Load Balancing one 2. Change the Cost parameters of the Logical LB Workspace Server and the underlying Workspace Server (Options > Advanced > Performance) in order to have quota restricted to 2 sessions maximum per user 3. [ You might have to create in Metadata a duplicate Server object (the last level under 'Workspace Server') ] 4. Enable a higher level of Object Spawner log verbosity , change your parameters set (2.) iteratively and check if this works.   In theory, a pooled workspace would be simpler but Clients like SAS EG as far as I know cannot use these kind of multi-sessions pooled servers to tun a SAS session (?).   HTH ... View more

Hello,   If you want to ask SAS for any improvements, please feel free to post your feedback into the "SASware ballot Ideas" community. SAS listens, duly answers & even implements eventually 😉 : I speak out of experience.   Menu List "Find a Community" > SASware ballot Ideas   For your particular concern, from my point of view, this is quite independent from SAS or any file-based PC tool you might be working with on you PC.I remember the same sort of issues 10 years ago for Window XP/Windows 2003 and another antivirus. Those antivirus sometimes run (purposely) intrusive request at such low level as "I/O transaction" level, meaning every time your SAS session writes or reads a file portion stored on disk (list of blocks).    Updating the antivirus exclusion list with  SAS PC executable "sas.exe" or SAS table filenames extension (*.sas7bdat, *.sas7butl etc.) is sometimes mandatory to disable this behaviour and reclaim SAS full speed !   ... View more

@AndrewHowell wrote:   ...  So now I'm looking at: how to compare metadata packages & report on differences how to flag if an object in a package is checked out in one of the Dev environments. Hope this kicks off some good discussions.   You can use the ImportPackage tool with the -noexecute option : that would print out the SPK's content but, unfortunately, not at the smallest level : for instance, table columns might not be displayed, only column table name...   ObjectType /folder_path/ObjectName   With such a report, you could then launch a request into each of the Dev Repo project to look for any check-out status : a little bit time-consuming, perhaps with large SPK. ... View more

@AndrewHowell wrote:   ...  Scenarios: Modify a table metadata definition and/or a DI job (which may also change table definitions) in one Dev platform Modify a parameterised stored process (which is not metadata-associated with any specific table and/or job) in one Dev platform Probably others, but they are the main ones Wondering about security models (ACTs, user groups, etc) Issues: How to determine impact analysis on other Dev platforms. How to merge changes from different Dev platforms into a Test environment.    Interesting case, thanks for sharing !     I would suggest, maybe, to duplicate the multiple Dev SAS MD respositories into a single instance with several custom, each CopyDev_n ( CopyDev_1, CopyDev_2 etc.) synchronised with a custom repo. There might be integrity issues with specific object types like Libraries if the multiple Dev_n share same named Libraries, or Generated Transformations (a very specific kind of object as regards integrity rules). Then the automatic synchronisation processes will rely on some rules to apply the changes, rules to be explicited in order to know which change has prevailed eventually. Or this process can be made manually at regular intervals in order for a "Data steward / Data team" to decide how to reconciliate the changes.   Once the changes have been accepted, they would be retro applied to each initial Dev repositories impacted then safely exported towards a single Test environment, I suppose.   Process would look like :   1)  Dev_1 => { CopyDev_1 , ..., CopyDev_n } => Merge and reconciliation   Dev_2 => { CopyDev_1 , ..., CopyDev_n } => Merge and reconciliation  ... Dev_n => { CopyDev_1 , ..., CopyDev_n } => Merge and reconciliation   2) Evaluate impact from { CopyDev_1 , ..., CopyDev_n }   3) if necessary apply changes into several customs repo { CopyDev_1 , ..., CopyDev_n }   4) export SPK with changes from CopyDev_i impacted => Dev_i  export SPK with changes from CopyDev_k impacted => Dev_k    5) export changes from Dev to Test   This isn't very straightforward but at first thought the only practical solution I could come up with.       EDITED ... View more

Thanks Chris, this way it works 🙂 ... View more

Hi Don,   Thanks for sharing. This looks like a must read. Now SAS Communities feels more &more like sascommunity.org with such great articles.  I noticed a small issue though,  being unable to display the Slides attached to the post. Maybe my own browser (chromium) is bugging ?   Ronan    Edited ... View more