About AndrewHowell

AndrewHowell · ‎09-30-2018

@thanikondharish - have to agree with @Patrick. Try both, decide and post your reasons here. While you're at it, you can also try my favourite (simplest & unambiguous): flag=ifn(sex='F',1,0);

AndrewHowell · ‎09-24-2018

@Ullsokk, SAS will (generally) perform faster tasks on SAS-proprietary data formats. ("In-database" processing is a separate discussion.) If you are concerned about file locks on SAS tables, then why not emulate in SAS what is almost standard in relational databases - don't access the data tables directly(which then lock), instead VIEW the data through a data-step or proc-sql view.

AndrewHowell · ‎09-20-2018

When creating the stored process, did you register it to use a workspace server or the stored process server? (Should be stored process server, which uses a shared credential).

AndrewHowell · ‎09-19-2018

@Ramakanthkrovi - I only suggested EG as the simplest way to create the stored process. The stored process can (should?) be able to be executed by any SAS (metadata) client: EG, Visual Analytics, Add-In for Microsoft Office, Stored Process web application, etc.

AndrewHowell · ‎09-19-2018

Okay, here's my thought logic on this issue: ERROR: Physical file does not exist, C:\WINDOWS\system32\&path\data\mp_traffic.csv. WARNING: Apparent symbolic reference PATH not resolved. For some reason, the PATH macro variable is not being set - without having access to the actual EG project, I'll assume there's some SAS code in an AUTOEXEC process flow which is not running, possibly because the option to automatically run the AUTOEXEC process flow is not set in the user's EG options. So, where does C:\WINDOWS\system32 come from? When referencing files and/or folders, if you do not specify an absolute path (which the PATH macro variable should do), then it's a path relative to the "current folder". Where this folder is depends on things like whether or not you have set the SASINITIALFOLDER system option, or how you invoked SAS. For more information on how the current folder is determined, click here. A little bit of cheat code reveals the location of the current folder. (There may be better ways, but this works for me.) libname MyTmp "."; /* Set libref to current folder */ %put %sysfunc(pathname(MyTmp)); /* Show the path of the libref */ libname MyTmp clear; /* Clear the libref */ I'm guessing for some it will be set to C:\WINDOWS\system32. But you'll still have to work out why &PATH is not being set correctly..

AndrewHowell · ‎09-17-2018

@Cynthia_sas - can I suggest a little macro logic prior to assigning any macro variable to throw a well-worded error if the variable if not set? A nice big capitalised "ERROR:" message might get the user attention and assist in rectifying the issue. Just a thought..

AndrewHowell · ‎09-17-2018

Can you please supply the code you executed and the subsequent log? It looks as if a variable called &Path was meant to be set prior to running the code, but is wasn't, so '&path' is parsed as a literal string rather than a macro variable. Because the path was not set, it defaults to C:\WINDOWS\system32. But if you could supply the code & log, we can be more accurate regarding the error.

AndrewHowell · ‎09-16-2018

Read: "SAS programs similar to Microsoft's SSRS"

AndrewHowell · ‎09-16-2018

@SASKiwi - I think @Ramakanthkrovi is referring to the Microsoft SQL Server Reporting Services (SSRS - I don't think SAS "does" 4-letter acronyms..) being able to call pre-defined code.

AndrewHowell · ‎09-13-2018

Elsewhere (Enterprise Guide) create a SAS stored process with prompts When designing a Visual Analytics report, add a Stored Process object. Other VA objects (report/section filters, etc) can create & populate parameters; these parameters can be passed to the VA Stored Process object, which can consume them as macros.

AndrewHowell · ‎09-13-2018

Hey @ShelleySessoms - I've registered! 10:30pm works for me, although I may not last til 2am if I'm working the next day, so will probably fall back on the recording.

AndrewHowell · ‎09-12-2018

"We don't want to enable auditing for VA cause we already have same performance issue, and, if it's possible, we don't need to add overhead." So how do you intend to audit what you are doing in order to know what needs to change - including auditing again to verify improvement - without turning on auditing? You have an issue - ok, accept that your issue affects performance, but also accept that in order to rectify the issue means (temporarily) turning on auditing to gather appropriate metrics to address the underlying root cause.

AndrewHowell · ‎09-11-2018

You want to audit without enabling auditing.. hmm.. What auditing do you NOT want to enable? Why not? Do (or can) you enable extended monitoring? If so, you should be able to use the track who has accessed which reports. Check out the Environment Manager's User Guide - if there's not an out-of-the-box report, you should be able to easily clone a report and customise it to your needs.

AndrewHowell · ‎09-10-2018

I'm doing the same thing - understanding the relationship between SAS & Hadoop and coming up with best practices to get programmers to use Hadoop effectively without creating horrendous SQL joins with non-Hadoop tables & causing massive I/O pipeline blockages.. I suggest you review the following documentation: SAS and Hadoop technology: Deployment Scenarios (to understand your infrastructure) SAS 9.4 In-Database Products: Administrator's Guide (especially Ch 5: Administrator's Guide for Hadoop) SAS and Hadoop Technology: Overview (especially Ch 4: What SAS Technology interacts with Hadoop?) SAS LASR Analytic Server 2.7: Reference Guide (which explains the in-memory procedures) None of the software is "free" - there is some Hadoop functionality which comes with Base/SAS, but ideally you'd require at least the SAS/Access to Hadoop engine, and - depending on your requirements - possibly some in-database accelerators.

AndrewHowell · ‎09-10-2018

Thanks, Simon - will do. Chat soon.

Online Status	Offline
Date Last Visited	‎04-30-2023 01:46 PM