I forgot to mention that int[] is sufficient for most of our numeric data. We have some key fields stored as long integers which we will store as character in SQL . Since much of this data is used for modelling, the users have agreed that numeric precision is not a priority compared with storage capacity. ... View more

The intention is to add data change control which seems more manageable in SQL Server using change tracking. Also, a lot of the data might benefit from partitions - concatenating multiple periods using SQL views for time series analysis. SQL Server seems to have better view performance than SAS but it is more difficult to measure. ... View more

Thanks for pointing me to the FedSQL paper - very useful reference. proc sql _method lets me look under the covers when testing.  ... View more

Thanks. I have been asked for an initial assessment and don't have many details yet. Since a lot of workload is moving from on-prem servers to Azure, I am assuming Azure Active Directory will replace our local domain controllers. SAS94 will stay local for at least the next 2 years.   ... View more

Thanks for the response. It looked like it was possible and I hope my organisation is prepared to support Kerberos/IWA/NTLM. For once, there is some budget.... ... View more

Getting the owners sometimes needs Admin rights but not always. Here are 4 different outputs :   # Compact view for pasting into email Get-ChildItem "D:\SASWork" -File -recurse | select Directory, Name, length, <# path, filename,#> lastwritetime, @{Name="Owner"; Expression={ (Get-ACL $_.Fullname).Owner }} | Sort-Object -Descending length | Out-GridView # Write to standard output for selecting details Get-ChildItem "D:\SASWork" -File -recurse | select Directory, Name, length, <# path, filename,#> lastwritetime, @{Name="Owner"; Expression={ (Get-ACL $_.Fullname).Owner }} | Sort-Object -Descending length | Format-Table # Write to csv for DSD parsing with SAS Get-ChildItem "D:\SASWork" -File -recurse | select Directory, Name, length, <# path, filename,#> lastwritetime, @{Name="Owner"; Expression={ (Get-ACL $_.Fullname).Owner }} | Export-CSV -Path D:\sas\Batch\datafiles\D_SASWork_Files_$(get-date -f "yyyyMMdd").csv -NoTypeInformation # Pre-req : Install-Module ImportExcel -AllowClobber -Force # Write to xlsx Get-ChildItem "D:\SASWork" -File -recurse | select Directory, Name, length, <# path, filename,#> lastwritetime, @{Name="Owner"; Expression={ (Get-ACL $_.Fullname).Owner }} | Export-Excel -Path D:\SAS_Users\AFarrer\xlsx\D_SASWork_Files_$(get-date -f "yyyyMMdd").xlsx ... View more

@MarcoGhiglieri Adding members to 'SAS General Servers' is a good suggestion.   Sadly, my users have little interest in using SAS Stored Processes even though they are heavy Excel users with the SAS addin enabled after some effort on my part.....   I think I will move the domain service account to a SAS Batch account used for writing to Prod SQL Server tables.    On another note, I really miss attending SGF and meeting other SAS admins. Online is not the same.... ... View more

Got it. Thanks Nigel.   I had forgotten that the userid was added to 'SAS General Servers' group so that Stored Processes could access SQL Server using ODBC.   Our site is all Windows Server 2019 with a lot of integrated authentication that also works with Azure. Any process running as an AD domain user will authenticate without userid or password. Great in most cases but tricky for service accounts used by regular users. Connection to SQL Server 2019 with userid/password is actually blocked. For testing, I use runas a lot.   However, I am very disappointed that the Search and Advanced Search could not find the userid. I tried with and without '\'   Thanks to everyone who responded so promptly.     ... View more

Thanks for the feedback. Making date-stamped versions of files is the current approach. I have seen MS Visual Studio has good interfaces to Azure but we are stuck with VSCode and git bash.    Our Windows Server 2019 SASv94M8 configuration is relatively simple and could be managed by non-SAS admins. They like Azure DevOps,  scripts and concise documentation but there are no guidelines for configuration management - yet.      ... View more

The JSON has a bunch of info which may be better but this primitive approach seems to be working over the past few weeks :   libname lasttabs clear ; libname lasttabs json "%sysget(APPDATA)\SAS\SASStudio\preferences\editTabContentPane.SWE.lastTabs.key" ; data work.recent_progs (keep = nowdt uriparent name moddt) ; set lasttabs.maintabs ; JSONstringSecs = input(modifieddate, 13.) / 1000 ; moddt = JSONstringSecs + intnx('second','01jan1960:00:00:00'dt,'01jan1970:00:00:00'dt) ; nowdt = datetime() ; format nowdt B8601DT15. ; run ; proc sql ; create table mydata.prev_progs as select * from mydata.recent_progs ; insert into mydata.recent_progs select * from work.recent_progs where name not in (select distinct name from mydata.prev_progs) ; select nowdt , uriparent , name , moddt format = datetime. from mydata.recent_progs order by 3 desc ; quit ;   ... View more

Success!  I ran an update from v15.0 (2 months old) to v16.0 and was presented with an SAS Remote (IOM) option for a new connection. Looking good so far. Thanks     ... View more