|Date: ||Mon, 27 Jun 2011 17:12:40 +0000|
|Reply-To: ||Michael Raithel <michaelraithel@WESTAT.COM>|
|Sender: ||"SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>|
|From: ||Michael Raithel <michaelraithel@WESTAT.COM>|
|Subject: ||Re: Tracking SQL progress|
|Content-Type: ||text/plain; charset="us-ascii"|
David Kellerman posted the following:
> I am updating a remote access database using the PROC SQL and EXECUTE
> statements below.
> %MACRO SENT(TBNAME);
> EXECUTE (UPDATE %STR(&)TBNAME SET SENT=1 WHERE MRN=999999999 AND DOV=
> #03/28/2007 # AND FORM=23 ) BY PATH %STR(;)
> %MACRO UPD(DBNAME,TBNAME);
> PROC SQL FEEDBACK PRINT;
> CONNECT TO ACCESS AS PATH (PATH="&PATH\&DBNAME") ;
> DISCONNECT from PATH;
> The process works but does not appear to complete, actually appears to
> upon attempting completion. The SAS session says "PROC SQL running"
> does so until I cancel executing statements. I have tried the PROC SQL
> options FEEDBACK and PRINT but get no listing in the log.
> I know that there is a return code sent for each execute statement (I
> showed 1, there are several thousand), but I can't seem to get that
> working. Ideally I would like to see in the log the execute statement
> followed by "RECORD UPDATED" or something of the sort. This might give
> an idea why the hang at the end.
> Any suggestions will be gratefully attempted. Thanks to all in
David, in addition to Joe's good advice, you might want to check out the SASTRACE option. That allows you to get information on what the DBMS is actually doing to process SAS-to-DBMS code you submit. You can find a write-up in the online SAS documentation:
...and in other SAS online documentation; if you search.
David, best of luck in all your SAS endeavors!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
SAS Press Author Page: http://support.sas.com/publishing/authors/raithel.html
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
Author: The Complete Guide to SAS Indexes
The degree of normality in a database is inversely proportional
to that of its DBA. - Anonymous