04-05-2016 06:53 AM
we have environment manager setup and it's working fine as we observe that the artifacts datasets have accumulated over 100 gigs. however, we are running out of server space. just wondering if we just move those artifacts datasets to another drive, would it impact the process? \SASEnvironmentManager\emi-framework\apm\Data\artifacts talking about the files in this folder. if we remove them would the .bat file re-create those files again later? thanks.
04-05-2016 10:36 AM
I don't think removing the files is a good idea. There is SAS code that manages the content and lets you prune the data.
The exact path might vary depending on where SAS is installed, the following code...
[Path to SAS installation]\SASEnvironment\SASCode\Jobs\apm_archive_data.sas
In the top of that code there is a path, %let sasUsageDir=<path>; that points to where APM data is stored. The code provides a template for archiving/deleting data over a specified age from the artifacts directory to the archive directory in \APM\Data\. You could set the archive directory to another location. By default all of the files wind up in \APM\Data\ so that directory can grow quite large.
Does this help? Do you see the code in your SASHome?
04-07-2016 08:01 AM
oops. sorry. i think we have a problem with the scripts. the data steps creates temp tables after delete records. but the server doesn't have enough space for temp table anymore. sql delete does not physically deletes the records so the file size is still the same. any ideas? thanks.
04-07-2016 10:07 AM
Looking at the code I see it uses a data step for the deletes, not proc sql. The data step should delete the tables rows as long as the data steps finish.. The proc sql is just used to extract the backups to archive. If the server doesn't have room for the temp tables then the delete data steps will fail and all will be left as it was. You can try setting the saswork and temp to a different larger disk. That should allow all the steps to finish.