Hi,
have you contacted Tech Sup yet? If not, that might be something to run by TS. https://support.sas.com/techsup/contact/
Thanks
Anja
Can you explain to me what you mean by disk? Is this a single hard drive in your computer? If so, we have figured out your problem. A single hard disk drive can not give you the IO performance needed for SAS.
Again, can you give us more specifics on the disks used to create the E:\ file system.
Our E drive is a total of 14 disk using Raid-10. The E Drive is used to write our data sets to and is also used as our work directory.
I got pulled into another project the end of last week. How many concurrent SAS jobs are running at any given time on your system? 7 drives may not be enough to give you the 100 MB/sec/physical core in your system that the SAS WORK file system needs.
I am very happy to continue helping you with this. Our best practice is to never have SAS WORK share the same disks as your permanent SAS data files.
Please read these two papers to see if they help address some of your questions. And then email me at my SAS email address to continue the conversation (Margaret.Crevar@sas.com).
http://support.sas.com/resources/papers/proceedings16/SAS6201-2016.pdf
http://support.sas.com/resources/papers/proceedings16/SAS6761-2016.pdf
Put your permanent data on the SAN (this also makes mirroring across locations easier), and use an array of internal SSDs for WORK. And make sure that the whole data path (bridges, main bus, controllers) can handle the throughput of all disks. And make sure that all disks are included in the stripeset at any moment. It won't do if only 2 disks handle a given request.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.