thanks for the quick replies!   I don't see any other options then to create my own task, to make it not too complicated for business users   Using a library which is shared for every user is securitywise not a good option here. We also don't want our business users to have to write a proc contents to generate the table. ... View more

Hmm ok, it confirms what I was thinking.   Passing all the column names and labels as paramters which has to be entered by the user is not an option.    When we create our own custom task, It would probably solve it? But we don't have any experience with that. Any other suggestions?  ... View more

Thanks Andreas for sharing. I was planning to do the same as I don't see any other options then to store every table in metadata and use metadata scripting. ... View more

Yes correct but it will look at the physical table in the SQL server to base his metadata on, and the labels are not hold there?  ... View more

Correct.   When i run this code the dataset is created with variable a but the label is also "A".  ... View more

Hi,    I've solved it with putting the labels in my datastep statement which will load the data to hadoop from SQL database.   /* upload to hadoop with labels */ data &hdfsLibref..&outtable (/*debug optie: logupdate=yes*/ blocksize=64M label="&tableDescr."); set &_input; label &label_sql_dataset; run; ... View more

Is your code for column label? Or for the table label? ... View more

if you declare your library like libname &p_inputlibref meta library="&p_saslibname";   This is a connection to a SQL database.   proc sql; select strip(name) || "='" || strip(label) || "'" into :label_list separated by ' ' from dictionary.columns where upcase(memname) = upcase("&_INPUTREF"); quit; %put &label_list;   The only thing left is to apply this to the LASR table. At this point i'm still struggling with that because a proc datasets and modify is not allowed? ... View more

yes we have different metadataservers   we load from Eguide to hadoop to LASR. Ofcourse, it's not important what's in hadoop but we also have no labels in the LASR tables.   ... View more

thanks, we are trying to load data from Enterprise Guide to Hadoop and from Hadoop to LASR memory. The Eguide and Hadoop/LASR are on different metadata environments. When I do a copy of the dataset in enterprise guide to my work library with the meta libname statement it copies the labels. Thanks! But when we are running our code we will connect to the VA environment where we execute some parts of the code. In the VA environment we can run the full libname statement: LIBNAME MW1DM_05 SQLSVR DATAsrc=bisql2_o SCHEMA=MW1DM_05 AUTHDOMAIN="auth_bisql2_o"; But not this one: libname MW1DM_05 meta library="MW MV90 DM"; So do we have any other option then add this library to the metadata of our VA environment? ... View more

So you mean we have to use a meta libname statement? ... View more