Hi Folks,   I have a piece of SAS code that updates for a given user in Metadata (and a given Authentication doman of this particular user)  its Login-Credentials:  %macro update_login_in_metada(name, pwd, auth); data _null_; length uri_domain $256.; length uri_user $256.; length uri_login $256.; length name_domain $200.; length name_user $200.; * initialize "uri*" and "name_*" variables; call missing(of uri_: name_:); * initialize variable "nobj1"; nobj1 = -1; * write number of person objects found in metadata into "nobj1"; nobj1 = metadata_getnobj("omsobj:Person?@Id contains '.'", 1, uri_user); * loop through all found person objects; if nobj1 > 0 then do; do i = 1 to nobj1; nobj2 = metadata_getnobj("omsobj:Person?@Id contains '.'", i, uri_user); rc1 = metadata_getattr(uri_user, "Name", name_user); * lookup person object; if name_user = "&name." then do; * get corresponding Login-Account of Auth-Domain; nobj3 = metadata_getnasn(uri_user, "Logins", 1, uri_login); * loop through all Login-Accounts of particular user; if nobj3 > 0 then do; do j = 1 to nobj3; nobj4 = metadata_getnasn(uri_user, "Logins", j, uri_login); nobj5 = metadata_getnasn(uri_login, "Domain", 1, uri_domain); rc2 = metadata_getattr(uri_domain, "Name", name_domain); if name_domain = "&auth." then /* update password for selected Auth-Domain*/ do; rc3 = metadata_setattr(uri_login, "Password", "&pwd."); end; end; end; end; end; end; run; %mend update_login_in_metada; It takes approximately 50 seconds for one user to run this step: %update_login_in_metada(johndoe, abc123, DBAuth) To me it seems, that the Data Step Metadata Functions are very slow... I know of the Metadata Procedure as a potential alternative way to update metadata. However, I do not know, how to set up/write the appropriate xml file structure as input to the procedure. Also, is the Metadata Procedure faster than the Data Step Metadata Functions?   Any help would be highly appreciated, FK21 ... View more

Howdy!   I am trying to use the PRESORTED option of PROC SORT to avoid multiple, very lengthy (~10 minutes) sorts.  However, I am finding that SAS sometimes does not accept that a sorted dataset is truly sorted when also using NoDupRec.   My dataset, labs, I have already sorted by all variables.  When I sort it with no options, SAS tells me it's already sorted.  When I add PRESORTED, it tells me it's already sorted.  But when I add PRESORTED and NoDupRec, it tells me the data is not sorted.  However, the meta data does show the data sorted (of course).  Does anyone know what's going on? 1125 proc sort data = labs; 1126 by _all_; 1127 run; NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds memory 1456.12k OS Memory 26644.00k Timestamp 03/26/2025 10:21:41 PM Step Count 50 Switch Count 0 1128 proc sort data = labs presorted; 1129 by _all_; 1130 run; NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds memory 1456.12k OS Memory 26644.00k Timestamp 03/26/2025 10:21:41 PM Step Count 51 Switch Count 0 1131 proc sort data = labs presorted noDupRec; 1132 by _all_; 1133 run; NOTE: Input data set is not in sorted order. When I tried a super simple example, it works fine. 1143 proc sort data = sasHelp.class out = class; 1144 by _all_; 1145 run; NOTE: There were 19 observations read from the data set SASHELP.CLASS. NOTE: SAS sort was used. NOTE: The data set WORK.CLASS has 19 observations and 5 variables. NOTE: Compressing data set WORK.CLASS increased size by 100.00 percent. Compressed is 2 pages; un-compressed would require 1 pages. NOTE: PROCEDURE SORT used (Total process time): real time 0.01 seconds user cpu time 0.00 seconds system cpu time 0.01 seconds memory 1213.43k OS Memory 26636.00k Timestamp 03/26/2025 10:23:46 PM Step Count 56 Switch Count 0 1146 proc sort data = class presorted; 1147 by _all_; 1148 run; NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds memory 328.28k OS Memory 25860.00k Timestamp 03/26/2025 10:23:46 PM Step Count 57 Switch Count 0 1149 proc sort data = class presorted noDupRec; 1150 by _all_; 1151 run; NOTE: Sort order of input data set has been verified. NOTE: There were 19 observations read from the data set WORK.CLASS. NOTE: Input data set is already sorted, no sorting done. NOTE: PROCEDURE SORT used (Total process time): real time 0.00 seconds user cpu time 0.00 seconds system cpu time 0.00 seconds memory 328.28k OS Memory 25860.00k Timestamp 03/26/2025 10:23:46 PM Step Count 58 Switch Count 0 Thanks, Michael   ... View more