Hello, I'm designing a Data Mart solution on SAS. I have a couple of design question. The main fact table is a list of tickets. By business request each update to one of this ticket overwrites the last one instead of adding a row. This is the first problem, I'm afraid that an update of such a large table is more expensive than simply adding a row (we're talking of 100M distinct tickets). Another problem is that one field of this table consist of a text description of the ticket status. The variable lenght is defined at 2000 and multiplied for 100M rows I'm worry it will generate a table so big it'll be difficult to handle. How can I manage the text field? Do I keep it in the main fact table or do I treat it like a separated dimension (even if it has the same cardinality as the fact_table?) I'm thinking that many of the analytical jobs that use this table downstream don't need the text field so keeping it in a different table could improve join elaboration time but I also understand it's bad design. What's your advice? Thanks   ... View more

Hello,   I'm starting to figure out how to leverage stored processes exposed as web services. I'm starting to test Stored Processes with a PROC HTTP.   The code for the SP is this %global wsRC wsValue wsMsg returnString; %let wsMsg = someDate=&someDate; %macro runCode; proc sql noprint; select &statName( &columnName ) into :wsValue trimmed from &tableName ; quit; %if &sqlrc = 0 %then %do; %let wsrc=&sqlrc; %end; %else %do; %let wsrc=&sqlrc; %let wsMsg = ERROR: &syserrortext; %let wsValue = .; %let syscc = 0; %end; %mend; %runCode The PROC HTTP that uses this Stored Process is this %let hostName = 192.168.1.61; %let port = 7980; %let SASBIWS_path = /SASBIWS/rest/storedProcesses; %let stpName = /SAS Validation/SAS Stored Procedures/stp_02_ws; * * build parm list for REST XML request *; filename htin temp; data _null_; infile cards; input; file htin; put _infile_; cards4; <any> <parameters> <tableName>sashelp.cars</tableName> <columnName>invoice</columnName> <statName>MEAN</statName> <someDate>2016-01-17</someDate> </parameters> </any> ;;;; * * call STP as REST WS *; filename htout "/home/lasradm/Test/rest_test"; proc http method="POST" URL="http://&hostName:&port.&SASBIWS_path.&stpName" in=htin out=htout ct="application/xml" WEBUSERNAME="lasradm" WEBPASSWORD="sas" verbose ; run; * * display result *; data _null_; infile htout; input; putlog _infile_; run; filename htin clear; filename htout clear; This works fine, on the log I can see the result embedded in XML code. Now I tryed to write a similar program passing different parameters to the SP. Didn't work. I restrict the problem on the library. As long as I use SASHELP it works. If I use a library defined by me (with all the permissions) it gives this generic error   HTTP Status 500 - Request processing failed; nested exception is com. sas.web.services.WSException: SAS completed with nonzero SYSCC '1,012'. SYSMSG: '' Can't figure out where the problem lies. I'm using SAS 9.4   edit: I found this code on this topic https://communities.sas.com/t5/Administration-and-Deployment/REST-in-webservices-in-sas-9-4-m3/td-p/295647 ... View more

This is second hand and I have not much info on the problem, googling the error code give me nothing. This is the code that generate the error   LIBNAME NAME SASIOLA  TAG=HPS  PORT=10011 HOST="host_address" ; LIBNAME LIB1 "/path";    data pro1;  set LIB1.case (obs=100); run ;     proc lasr port=10011 data=work.pro1 add;    performance host="host_address"; run;   The error returned is  "ERROR: Failed to load analytic extension for the distributed computing environment."   What could be the trouble? What questions could I ask to better define the situation? For what I understand the data is in HOSTa and the LASR is running on HOSTb ... View more