Importing LASR Tables in Management Console Target Library not Found

[DavidPhillips2]

When importing LASR tables in management console some tables auto fill the target library destination while others do not.  The library name and physical name are different between the source and target server.  Why would one table recognize the target library while others do not?

I’m asking about LASR tables but I’m guessing my question can be generic.

[SASKiwi · Accepted solution]

I'm assuming you are referring to the importing of LASR table metadata definitions via the Import SAS Package functionality, rather than actual SAS LASR tables.

I'm curious to know why you are using this approach when you can import LASR tables AND update their metadata definitions all in one go using the VA Data Builder:

http://support.sas.com/documentation/cdl/en/vaug/69957/HTML/default/viewer.htm#p018nyo71g4dpzn1nrr0x...

[DavidPhillips2]

I found that I did not need to import the metadata for the LASR tables since I am running data prep queries that create the LASR tables on the target server.

[JuanS_OCS]

Hello @DavidPhillips2,

yours is an interesting question. However it is a bit hard to give you a proper answer without additional knowledge of your metadata, and which probably you cannot/should not share here.

There are a lot of rules that apply during the update metadata and import packages processes, as what happens when there is a table with similar name on a same LASR server (even if they are in different metadata folders).

From my point of view, your best choice is to ask this question to SAS Technical Support because:

- They can securely give a look to your environment, if needed.

- They can have contact with the developers of specific components, of needed.

In other hand, as @SASKiwi mentioned, there are other ways to achieve what you need, but I wanted to focus on your question based on SAS Management Console.