BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
EyalGonen
Lapis Lazuli | Level 10

Hi all,

 

I would like to create a process which automatically unloads tables from CAS based on their last accessed time.

So for example, if a CAS table loaded to memory was not accessed in 48 hours then unload it from memory.

 

Is this possible? Anyone did anything like this?

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
gwootton
SAS Super FREQ

Take a look at the built in Sample unload job's "unloadAccessThreshold" parameter:

CAS Table State Management - Unloading Data
https://go.documentation.sas.com/doc/en/sasadmincdc/v_069/caldatamgmtcas/n150v9svjp42ron1hn9r496xj49...

 

Edit: To fully answer the question of generally how to determine the last accessed time for a CAS table, this is an attribute of the table so can be retrieved using:

--
Greg Wootton | Principal Systems Technical Support Engineer

View solution in original post

2 REPLIES 2
gwootton
SAS Super FREQ

Take a look at the built in Sample unload job's "unloadAccessThreshold" parameter:

CAS Table State Management - Unloading Data
https://go.documentation.sas.com/doc/en/sasadmincdc/v_069/caldatamgmtcas/n150v9svjp42ron1hn9r496xj49...

 

Edit: To fully answer the question of generally how to determine the last accessed time for a CAS table, this is an attribute of the table so can be retrieved using:

--
Greg Wootton | Principal Systems Technical Support Engineer
EyalGonen
Lapis Lazuli | Level 10

Thanks @gwootton  - you're always a great help!

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 2 replies
  • 445 views
  • 1 like
  • 2 in conversation