Exploring, modeling, predicting and reporting with SAS Visual Analytics and SAS Visual Statistics

SAS Visual Analytics Autoload

Reply
Contributor jei
Contributor
Posts: 59

SAS Visual Analytics Autoload

Hi!

 

I'm using SAS Visual Analytics 7.3 and trying to use the autoload. While reviewing the attached log file of the autoload, it seems that the table was loaded to LASR server. However, the table was not in the list of tables in Administrator whenever I checked it. May I know if the table was successfully loaded based on the log file? And are there specific ways to configure the autoload feature?

 

Thank you very much!

Super User
Posts: 1,098

Re: SAS Visual Analytics Autoload

Hello,

 

In short, this log file only says there is one table already on LASR, and no tables or files to be loaded.

 

NOTE: SCANNING LASR SERVER
TABLES:
      DAMARKETPRICES2013
--------------------------------------------------------
NOTE: IMPORT
NO NEW FILES TO IMPORT
--------------------------------------------------------
NOTE: LOAD
NO NEW TABLES TO LOAD TO LASR
--------------------------------------------------------

 

If you put a file on an autoload folder and it is not loading, some considerations. There are several autoload folders, each of them with a process to schedule. And you can even create additional custom autoload folders!


What can be happening in your case, is that you are dropping data in an autoload folder, on which you don;t have scheduled the autoload process on the Windows Scheduler. Maybe you have scheduled autoload, but on a different folder.

 

The folder you need to drop the data into is C:\sas94\config\Lev2\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\AutoLoad\VALIBLA

 

 

Contributor jei
Contributor
Posts: 59

Re: SAS Visual Analytics Autoload

Hello @JuanS_OCS,

 

Since I dropped my data in VALIBLA folder in

C:\sas94\config\Lev2\AppData\SASVisualAnalytics\VsualAnalyticsAdministrator\AutoLoad\VALIBLA

 

Should I use the schedule.bat in the VALIBLA folder in 

C:\sas94\config\Lev2\Applications\SASVisualAnalytics\VisualAnalyticsAdministrator\VALIBLA

OR

I'll use the schedule.bat in

C:\sas94\config\Lev2\Applications\SASVisualAnalytics\VisualAnalyticsAdministrator

 

Thank you very much!

New Contributor
Posts: 3

Re: SAS Visual Analytics Autoload

Hi Jei
The standard is to put the data you want loaded into

C:\sas94\config\Lev2\AppData\SASVisualAnalytics\VsualAnalyticsAdministrator\AutoLoad

not

C:\sas94\config\Lev2\AppData\SASVisualAnalytics\VsualAnalyticsAdministrator\AutoLoad\VALIBLA

(i.e. not in the VALIBLA folder). The \Unload folder is for when you want to delete the VA table and the \Append folder is for when you want to append data to an existing VA table.

And the standard schedule.bat to use is in

C:\sas94\config\Lev2\Applications\SASVisualAnalytics\VisualAnalyticsAdministrator

These are the standard locations, however I recommend changing the autoload folder to a location away from the standard config files, as you don't really want users writing files into your config folder structure. But that's another topic!
Note, I teach the VA Admin course which covers this and other ways to load data.
Contributor jei
Contributor
Posts: 59

Re: SAS Visual Analytics Autoload

Hi @Kiwi_Colin & @JuanS_OCS,

 

I tried dropping the data into \VALIBLA folder then use the schedule.bat in \VALIBLA folder AND I also tried to drop the data into \AUTOLAD folder then use the schedule.bat in \AUTOLOAD folder.

 

But I found no difference on their autoload logs. Still no table was loaded in LASR.

 

I really don't know why. Are there steps that you can share for autoloading tables? Or may I know what's wrong?

 

Attached are the two logs I got.

 

Thank you very much!

Super User
Posts: 1,098

Re: SAS Visual Analytics Autoload

Hello @jei,

 

I would expect it to be the first one.

The second one is good if you will drop data under C:\sas94\config\Lev2\AppData\SASVisualAnalytics\VsualAnalyticsAdministrator\AutoLoad

Ask a Question
Discussion stats
  • 5 replies
  • 485 views
  • 0 likes
  • 3 in conversation