topic Re: Autoloading Tables in SAS Visual Analytics

Autoloading Tables

angeliquec — Fri, 27 Jun 2014 14:41:16 GMT

Is it possible to autoload tables from multiple sources (from host) to multiple metadata folders directed to a single LASR server?

We'd like to have the tables in different metadata folders for easier changing of permissions for each table.

Re: Autoloading Tables

avinesh — Mon, 30 Jun 2014 06:19:49 GMT

Hello Angeliquec

I hope this code will help you to load a table automatically from memory

libname sas startserver port=10010 tag='hps';

data sas.demo;

set sashelp.demo;

run;

Re: Autoloading Tables

PeterWijers — Mon, 30 Jun 2014 11:49:00 GMT

Hi Angeliquec,

I only use one source so there no answer.

I use a usergroup to assign the table read/write rights and its easy to control.

I do not understand why you would like to have the tables in multiple metadata folders if this way of easy permission assigning works well.

So no ACT's but just Usergroups with read rights, and assigning users to them.

If you need more information, be my guest.

Greetings Peter

Re: Autoloading Tables

angeliquec — Wed, 02 Jul 2014 16:31:21 GMT

Thanks for the responses Avinesh and Peter!

Aside from Autoload, I have found another code that not only uploads data to LASR, but also registers the metadata.

data valibla.cars;

set sashelp.cars;

run;

proc metalib;

omr

(library="/Products/SAS Visual Analytics Administrator/Visual Analytics LASR"); /*Path of the LASR Library - do not change*/

folder="/Shared Data";

select=("cars");

run;

Re: Autoloading Tables

jakarman — Sun, 06 Jul 2014 17:56:34 GMT

Angeliquec, do you have access to the vaag.pdf (SAS-VA 9.4) reload is described by autostart/autoload page 20). It is not vague although this document has that (dutch) name.

Aside from the autoload question your question seems to be an having different user groups using SAS VA needing different access definitions. This can be a mandatory approach with more demanding higher priviledged data (privacy, finance, health) in that case I would advice to review the bisecag also (security admin guide).

Your latest posted code is quite common to SAS metadata administration and definition (Bi DI).