BookmarkSubscribeRSS Feed
Sandhyaa
Calcite | Level 5

We have serveral jobs running parallely. Each job will make an entry to the audit dataset.So we want to avoid locks on the audit dataset.

Please suggest an optimised approach for this requirement.

1 REPLY 1
LinusH
Tourmaline | Level 20

If you can't control the jobs so they won't write to the audit table at the same time, there are a number of options available to you.

  1. have the audit table store in a schema that supports simultaneous updates. Examples of this is  SAS/SHARE, SAS SPD Server, end practically any other RDBMS.
  2. Make a macro that checks if a lock is available on the audit table, if not, wait for n seconds and then retries, and so on.
  3. Have the individual audit tables. They could be appended in an ordered fashion once a day (or any other time interval that suits your needs).
Data never sleeps

sas-innovate-2024.png

Don't miss out on SAS Innovate - Register now for the FREE Livestream!

Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.

 

Register now!

How to connect to databases in SAS Viya

Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 2082 views
  • 0 likes
  • 2 in conversation