Quick VA Tip: How to load a LASR table

[#1]

Quick VA Tip: How to load a LASR table

Need to load a LASR table into memory without going into the VA application? There are many ways to do this: it’s as simple as grabbing the code that loads the table and then either:

1. As part of your code to start a LASR server, you can add the code to load the tables you want into memory.

  OR 

2. You can use the auto load library feature, this will do the same as above without having to code.

Ted Werner

[SusanMiller_TNC_]

Thanks Ted - a couple questions:

1. Is there any way to run the auto load feature on more than one directory/SAS Library and have it load to multiple LASR libraries?

2. Are there pro's or con's to having multiple LASR Libraries?

Thanks for the tip

[ted_werner_sas_com]

1. Is there any way to run the auto load feature on more than one directory/SAS Library and have it load to multiple LASR libraries?

Out-of-the-box, you have one Public LASR Server that post-installation can be configured as auto load.  Essentially, you can create multiple LASR Servers to behave with the auto load functionality – you simply need to copy the necessary scripts and add the corresponding metadata pieces.  These instructions are outlined in two places.  I have heard of customers creating more than one LASR server with auto loading configured to support different departments.

The post install instructions for the Auto Load feature is documented in the VA Administration Guide:  http://support.sas.com/documentation/solutions/va/6.2/vaag.pdf

Location in PDF:  Fundamentals  \ Loading Data to Memory \ Automated Loading.

2. Are there pro's or con's to having multiple LASR Libraries?

Pro’s to multiple LASR Servers:

- This is the only way to restrict the list if available sources from Explorer/Designer:  deny ReadMetadata for different users/groups and then only those with access can see what tables have been loaded into the LASR server. 

- If you have auto load configured for multiple LASR servers then this could be easier to manage what data stays in memory – if it’s only a single LASR server it might be more difficult to track down the owner of tables to determine what needs to be unloaded.

Con’s to multiple LASR Servers:

- No way to restrict how much memory a LASR Server can use – only total memory of LASR Servers combined can be restricted (for example, stop loading once 80% of the memory is used)  This cannot be defined per LASR Server, yet.

- If you have multiple LASR Libraries (esp with the auto load configured) then it is possible for one LASR server to hog the available memory if it is not properly monitored/managed

- Additional user/group administration overhead

- Additional auto load configuration required if you want the LASR Server to support auto load

Ted Werner

[ted_werner_sas_com]

Thanks for your interest if you have more questions feel free to let me know.   I hope that if anyone else has some content they might have created on loading to LASR feel free to share.

Ted Werner

[muralinori_sas]

Autoload works on a One-to-One relationship between the library and the LASR server.  a library points to a LASR server.

One can create multiple Autoload directories and point them to different LASR servers. 

If the tables are already registered, you can also use the GUI in the Admin to load the table to Memory.

All this is documented.

[kcook]

Hello,  Susan and I have tried to access the document referenced: http://support.sas.com/documentation/solutions/va/6.2/vaag.pdf but it requires an additional login that we don't have.  Would you please send us the document for review?  Thank you!

[anna_holland]

Hi kcook , we are looking into this! We will get you access to that document soon. Thanks!

Anna-Marie

[Pathak]

Hi Anna, Could you please give us credentials to open http://support.sas.com/documentation/solutions/va/6.2/vaag.pdf. or let the document available to be reviewed by everybody.

Thanks in Advance.