PROC SQL does not care of READONLY libname ?

CHUNantes — Tue, 30 Aug 2022 08:24:11 GMT

Hello.

We have two jobs that can run in parallel some times.

One job (A) will update a table and one job (B) just need to read the table.

So to avoid lock, job B use this statement :

LIBNAME r_thfcs "path_to_data" ACCESS=READONLY;

PROC SQL;
   CREATE TABLE work.toto AS
   SELECT *
   FROM work.titi,
        r_thfcs.tutu
   ;
QUIT;

But today, when job A run and try to update r_thfcs.tutu table, a lock was held by Job B !

Does it means PROC SQL is over READONLY access ?

Thanks.

Re: PROC SQL does not care of READONLY libname ?

LinusH — Tue, 30 Aug 2022 09:59:13 GMT

A READ lock is still a lock, if your other process need to update the table.

If you need concurrent read and qrites on the same table you need to use either SAS/SHARE, SAS SPD Server or an external RDBMS.

Another option is to schedule your jobs so thay don't access the table at the same time.

topic PROC SQL does not care of READONLY libname ? in SAS Programming

PROC SQL does not care of READONLY libname ?

Re: PROC SQL does not care of READONLY libname ?