I don't have insight in the future of Netezza per se, but my feeling is that customers are moving from (usually) expensive on site DW appliances to cloud based storage. So I can understand why management don't want to extend the use of it - sounds like that there is a road map? Question is what is the use case for this data, perhaps there is need for it outside the SAS domain? Perhaps you have some data/BI architects at your site that can guide you? ... View more

@C_Myers2211 wrote: The files are .txt.zip. So it's just a bunch of text in them. I'm not exactly sure of all the contents In that case there is no need to "store" the ZIP file in a library. You might want to create a SAS library to store the SAS datasets you ultimately generate form the TXT files so that the next time you want to reference that data you don't have to go through the process of converting the TXT into dataset(s).   You can use a fileref to point to the ZIP file and extract the individual members (files) from it.  You can point a fileref at the ZIP and treat it like a directory. filename myzip zip 'phystical_filename.zip' ; data want; infile myzip('individual_filename.txt') dsd truncover ; input var1-var5; run; Or you could make a fileref that points to an individual file. filename myfile zip 'phystical_filename.zip' member='individual_filename.txt'; Or you can skip that and just use the ZIP engine with the INFILE statement directly. data want; infile 'physical_filename.zip' zip member='individual_filename.txt' dsd truncover ; input var1-var5; run;   ... View more

In my experience you won't be able to crash SAS VA. All that will happen is response times in your browser pointing at SAS VA web pages will just increase to the point the VA web pages wont refresh at all. If you also monitor the SAS VA web server CPU usage will also flat line at 100% and possibly memory will max out. The bottleneck is all of the Java processes running on the SAS VA web server ... View more