hello, did you manage to find how to resolve this problem? ... View more

@amitvermajhs Here the docu link with examples as a starting point for you: http://go.documentation.sas.com/?docsetId=acreldb&docsetTarget=n05b4mygsvt845n1vnr6r5kchbjf.htm&docsetVersion=9.4&locale=en   If you want to stick with the code you've developed in SQL Developer then you need also to stick with user written code AND with Explicit Pass-Through.   That won't result in "best practice" SAS DI jobs (which should be metadata driven) but it's eventually the quickest and safest way for you to make things work. ... View more

@amitvermajhs Looking at your code and that you can execute this fully via SQL Developer I'd assume that also out of SAS everything runs fully in-database. Are you using explicit pass-through?   IF everything executes in-database then I don't really understand why you should be running out of WORK on the SAS side unless your WORK is really filled up (whole disk or your quota bit) OR you've got 1:M relationships in your lookups resulting in huge amounts of data.    Do you know how many rows your query actually creates? Have you ever run it directly out of SQL Developer with a simple SELECT COUNT(*) ? ... View more

Hi @amitvermajhs,   I asked @JohnnyS in SAS Training and he pointed out a couple of specific courses that may be helpful, but they are paid:   DataFlux Data Management Studio: Fast Track  https://support.sas.com/edu/schedules.html?ctry=us&crs=DQFT   Or   DataFlux Data Management Studio: Essentials: https://support.sas.com/edu/schedules.html?ctry=us&crs=DQDFPS   Both have classroom, live web, and eLearning options available.    Anna ... View more

In addition to Margaret's suggestion, here's something else you could use if you wanted to keep an eye on your sasworks during the day. More colours, less logging. Needs RHEL6.    https://github.com/Boemska/worktop   Nik ... View more

The filesize in dictionary.tables (or sashelp.vtable, which is a view to the same dynamic resource) is in bytes; the output of my UNIX command is in Kbytes, because of the -k commandline parameter. Without the -k, du would report disk blocks, which is not that informative, as it may be dependent on individual filesystem parameters. If you want to make both outputs comparable, divide the value from dictionary.tables by 1024.   By testing I found that there may be slight differences between the filesize value reported in dictionary.tables and proc contents (proc contents has the correct one). But that is in the range of a few K and therefore negligible. There is also a slight difference between file size and the du value, that depends on technical aspects of the filesystem interna. Also negligible. ... View more