for the record:   character compression increased my append time by 8 times. binary compression increased my append time by 20 times.   so i left compression off. ... View more

I don't like the duplicate metadata registration.   I built my own (very limited) table loader transformation to: - skip unmapped columns - optionally add the NOWARN option to PROC APPEND   For what it's worth, the code I currently have (which will surely evolve when I find errors in it and need additional options).   %macro x; %let rc = 0; %if (&loadstyle = REPLACE_DROP) %then %do; %if (&_OUTPUT_engine. = SAS) %then %do; proc sql; drop table &_OUTPUT.; quit; %end; %else %do; %put ERROR: REPLACE_DROP is only allowed for SAS data sets.; %let rc = 4; %end; %end; %if (&loadstyle = REPLACE_DELETE) %then %do; proc sql; delete * from &_OUTPUT.; quit; %let rc = &sqlrc; %end; %if (&loadstyle = REPLACE_TRUNCATE) %then %do; %if (&_OUTPUT_engine. = POSTGRES) %then %do; data _null_; call symput('postgres_table',strip(scan(scan(symget('_OUTPUT'),2,'.'),1,'"'))); run; %put NOTE: &=POSTGRES_TABLE; proc sql; connect to postgres (&_OUTPUT_connect); execute ( truncate "&POSTGRES_TABLE" ) by postgres; disconnect from postgres; quit; %let rc = &sqlrc; %end; %else %do; %put ERROR: REPLACE_TRUNCATE is only allowed for Postgres tables.; %let rc = 4; %end; %end; %if (&rc = 0) %then %do; proc datasets lib=WORK nolist nowarn; delete __LOAD; run; proc sql; create view WORK.__LOAD as select %let first = 1; %do i=0 %to %eval(&_OUTPUT_col_count. - 1); %if ((&&&_OUTPUT0_col&i._exp. ne ) or (&&&_OUTPUT0_col&i._input_count. > 0)) %then %do; %if (&first. ne 1) %then , ; %else %let first = 0; %if (&&&_OUTPUT0_col&i._exp. ne ) %then &&&_OUTPUT_col&i._exp; %else %if (&&&_OUTPUT0_col&i._input_count. > 0) %then &&&_OUTPUT_col&i._input; as &&&_OUTPUT_col&i._name %if (&&&_OUTPUT_col&i._type. = $) %then length=&&&_OUTPUT_col&i._length.; %if (&&&_OUTPUT_col&i._format. ne ) %then format=&&&_OUTPUT_col&i._format.; %if (&&&_OUTPUT_col&i._informat. ne ) %then informat=&&&_OUTPUT_col&i._informat.; %if (&&&_OUTPUT_col&i._label. ne ) %then label="&&&_OUTPUT_col&i._label."; %end; %end; from &_INPUT ; quit; proc append base=&_OUTPUT.( %let first = 1; %do i=0 %to %eval(&_OUTPUT_col_count. - 1); %if ((&&&_OUTPUT0_col&i._exp. eq ) and (&&&_OUTPUT0_col&i._input_count. = 0)) %then %do; %if (&first. = 1) %then %do; drop = %let first = 0; %end; &&&_OUTPUT_col&i._name %end; %end; ) data=WORK.__LOAD %if (%upcase(&warn) = NOWARN) %then NOWARN; ; run; %end; %mend x; options mprint; %x; ... View more

Excellent solution Paul. I am getting a forbidden error and to resolve the same, update the SAS webserver conf file setting to include the path (symlinks etc) some thing similart to below   <Directory ..../SAS/SAS94/config/midtier/Lev2/Web/WebServer/htdocs> #Options FollowSymLinks Options +Indexes FollowSymLinks Includes ExecCGI AllowOverride All Order deny,allow Allow from all </Directory>   Regards Prasad   ... View more

Hi,   I have one 94M3 environment that does not allow two domains with the same login without setting Outbound to Yes. I have another 94M3 environment that does allow two domains with the same login without setting Outbound to Yes.   What can be the difference?   Bart     ... View more

Hi Bart,   I think I misunderstood your initial message where you mentioned you still did not found the query on the metabrowse. Sorry for that.    Speaking about VA, I would tweak as less as possible and this seems a bit like tweaking the metadata. Experience says that you might solve a problem now, but easily generate additional problems (technical or functiona) or impact on time on other activities. But this is your server of course and you decide if you want to add an unsupported feature on your system or not.   Anyway, if you still want to follow this path: I think it is great that you now found the query on the metadata. Why can you not extract the query from the metadata? Maybe this should be the first question. What is your challenge? The XML query for the Metadata Interface?   In other hand, I trust that easiest solutions are generally the best. This one still seems to be a bit complicated. Let me explain:   You want to programatically load tables already registered by users in the metadata, and action them on a certain schedule. OK, fine. If you are able to enable that option for all the users, and ask your users to load (one time action) their tables to generate the SAS codes. From this moment, each time a user will load/register a table, it will generate the sas program. Then, you should be able to go through all the deployed sas programs and execute only the ones that are named with the "load" string on the name of the sas program. This will load all the tables,always. The script might find old scripts, which you can clean also programatically, or just let them to fail.   This is probably very similar to what you want to achieve with the metadata, therefore probably none of those options is preferable from the "twaeking" point of view, but I see this one easier and preferable from the maintenance point of view.   ... View more

I am told that the goal in the next release is to reduce the time to do maintenance upgrades from days to hours. The reason for the long time is the SAS mid-tier needs to be completely redeployed and retested.   If this does indeed happen then I can't think of any major technical reason to keep SAS VA separate.  ... View more

Thank you both. i agree to use a separate instance. regards Bart ... View more

Jan: Can you please help me on how to set up autoload features for multiple LASR libraries? Thanks ... View more

Hi Bart Did you get it to work? If so, have you succeded using user written SAS Studio tasks in EG? /Ole ... View more

All what i know is as in the SAS® 9.4 Language Reference Concepts Fourth Edition that : " The fonts that are supplied by SAS and the fonts that are installed by Microsoft are automatically registered in the SAS registry when you install SAS. Fonts that are installed after you install SAS must be registered manually in the SAS registry. " But your question still valid one. ... View more