About LinusH

LinusH

My SAS FIles is a folder in the Metadata server, and is set-up by default for each metadata user. It has nothing to do with SASUSER. The purpose is to have a playpen for you to store SAS content for your own needs, like testing/development. Typical object to store here could be Stored Processes, EG projects etc.

LinusH

You mean running in batch vs running inside DI Studio application? Please share logs.

LinusH

Gotcha, no, I can't explain that. Another way to see statements executed in a target dbms is to: options sastrace=',,,d' sastraceloc=saslog nostsuffix msglevel=i; Unfortenately this doesn't work for my OLEDB engine with DELETE, but perhaps it works better for you? 51 proc sql; 52 delete from oeldb.table 53 where id = 5254; SAS_SQL: Unable to convert the query to a DBMS specific SQL statement due to an error.

LinusH

From the documentation: "The FEEDBACK option expands a SELECT * statement into a list of columns that the statement represents."

LinusH

I think that SQLOBS reacts to the no of records from the select statment. Have you tried SQLXOBS (still undocumented ASFAIK)?

LinusH

Oh, I thought your comparison with PC SAS meant your were doing a "migration". That said, I would recommend to use SAS Viya pay-as-you-go (Azure, full Viya environement) for product evaluation scenarios. Could be easier to deploy. Microsoft Azure Marketplace Or, as I mentioned earlier, Viya Workbench (AWS, more suited for team/single users). SAS Viya Workbench | SAS

LinusH

I can't help you with this error, but as you phrase it "I want to report", I suggest you direct this issue to SAS tech support.

LinusH

If you execute using debug, you <might> get some more information out: options sastrace=',,,d' sastraceloc=saslog nostsuffix msglevel=i; What cloud does Snowflake reside on? And out of curiosity, what i SAS Fusion? I stumbled upon this , not sure if it's applicable: Multi Row Insert fails with "Failed to decrypt. Check file key and master key." · Issue #374 · snowflakedb/snowflake-connector-nodejs · GitHub A track to SAS tech support could be a good idea.

LinusH

Don't know, but if the secrecy of your data is important, permissions should be enforced on the data level, not in individual reports.

LinusH

If you are used to single user 9.4 installation, yes, Viya can seem like a nightmare. First, I think you need a Kubernetes specialist that can prepare the environment and guide you. IMO the default migraiton path for single users is SAS Viya Workbench.

LinusH

And of course thee are multiple ways of doing it in SAS: data have; length text $20; input text; datalines; abcd15ppppp bvcsf24dsfd cadadada30fdsfdsf ; run; data want; set have; col1 = scan(text,1,,'D'); col2 = scan(text,1,,'AI'); col3 = scan(text,2,,'D'); run;

LinusH

Since you mention EG I assume you are in 9.4 (even though EG is supported for Viya4). If you consider upgrading to Viya at some point, SSO is supproted there: SAS Help Center: Authenticate to Microsoft Azure Using Single Sign-On Ortherwise I think the AUTHDOMAIN option as already mentioned is the best method.

LinusH

I'm not a user of Intelligent Decision, but reading the doc it seems all functions applies to a whole dat grid. What would you expect to be the outcome by using a Group By?

LinusH

It's dependant on your specific contract with SAS. Talk to your SAS representative or the person in charge of your contracts. If not viable contact your SAS sales representative (or SAS Sales Channel partner if applicable). Generally speaking, SAS9 implementations are usually based on cores, and Viya4 per user. Solutions can seperate have other models, like % of turnover.

LinusH

Some starting points: SAS Help Center: Row-Level Security Examples of row-level security in SAS Viya - SAS Support Communities