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

How do I ensure the LASR query scheduler is accurate?

Accepted Solution Solved
Reply
New Contributor
Posts: 3
Accepted Solution

How do I ensure the LASR query scheduler is accurate?

Hello SAS community,

 

I'm having some trouble with the interactive query of a table from a DB (i.e., click 'Run') and the LASR table scheduler (i.e., click the clock symbol and set a nightly query for new records).

 

When I view my data prep setup within VA Data Builder, I've set the 'Where' clause to include all desired records after a given date (1st May). Running this with the interactive query produces the correct result:

77                 RECORDS.trn_dt >= '01May2017'd

The following day howerver, the table comes back missing the current month (July). Looking at the Batch Logs, I see that the SAS code on the scheduler reflects an older version of my Data Prep file, where I only wanted 1st May to 30th June:

77                 RECORDS.trn_dt Between '01May2017'd AND '30Jun2017'd

 

How do I ensure that the scheduler is using the current version of my files, and how can I manage the scheduler directly?

(SAS 9.4 using web browser interface SAS VA)

 

Thanks!


Accepted Solutions
Solution
2 weeks ago
SAS Super FREQ
Posts: 435

Re: How do I ensure the LASR query scheduler is accurate?

Did you change the filter after you created the schedule? Because existing schedules do not pick up changes made after they are created. You must reschedule based on the current state of the query.

 

 

View solution in original post


All Replies
Solution
2 weeks ago
SAS Super FREQ
Posts: 435

Re: How do I ensure the LASR query scheduler is accurate?

Did you change the filter after you created the schedule? Because existing schedules do not pick up changes made after they are created. You must reschedule based on the current state of the query.

 

 

New Contributor
Posts: 3

Re: How do I ensure the LASR query scheduler is accurate?

That did it! I was under the assumption that the scheduler would run the most recent version of the file, but re-scheduling the query fixed the issue. Thanks!

☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 2 replies
  • 162 views
  • 0 likes
  • 2 in conversation