Yes, you must have the Single User Edition of SAS Studio installed on the same machine as EG 7.1.  Also, make sure you can start SAS Studio (Single User Edition) by itself...  Start button->All Programs->SAS->SAS Studio (3.2 or later). Note: EG 7.11 will support the Enterprise Edition of SAS Studio in the next version of SAS Studio (3.4). ... View more

Similar to what Reeza said, if the libname statement works in Base SAS, and EG is connecting to SAS on the same machine (either locally or remotely), then submitting the same libname statement in EG (to the same server) should work. For example, if Base SAS and EG is on your local machine, the same libname statement should work in both (so long as you are submitting to the "Local" server in EG). If EG is on your local machine and you are submitting to a remote server, then the libname statement will work in EG if it also works in Base SAS installed on the server machine. In other words, the DSN has to exist on the host machine where the SAS server process is running. ... View more

You might be able to define a LASR library in the BI metadata environment, then use the Upload to LASR task to upload to that library.  The data would get loaded into LASR, but the table would not be registered in the VA metadata environment, thus couldn't be automatically used in VA. i don't completely understand your idea, can you elaborate on this? I haven't tried it, but given separate BI and VA metadata servers, I would think you could define a LASR library in your BI metadata server, so you have an output destination for the Upload to LASR task (when EG or AMO connected to the BI metadata server).  When you run the Upload to LASR task and "upload" to that LASR library, the data should get written (loaded into memory) to the LASR server (so you could use IMSTAT for example).  However, the uploaded table would not get registered in the VA metadata server, thus not automatically available for use in VA, losing a large benefit of the Upload to LASR task. If your goal is to use the data in VA and you have separate metadata environments, probably easier writing the data to a location that can be accessed by both environments, then using the VA tools to load the data. ... View more

The "Upload to LASR" task in EG and AMO is a very useful task for getting data prep/output from EG and AMO processing into LASR Analytic Server and registered for use in Visual Analytics.  However, as Linus pointed out, if you choose to maintain separate metadata environments, you are defeating the integration that task provides. You might be able to define a LASR library in the BI metadata environment, then use the Upload to LASR task to upload to that library.  The data would get loaded into LASR, but the table would not be registered in the VA metadata environment, thus couldn't be automatically used in VA. ... View more

The only source control system that EG (as of version 7.1) currently has direct integration with is Git.  However, as noted, you can use any other source control system external to EG, since EG just references those .sas files that are saved on disk.  In this scenario, you work on the .sas files from within EG, save them to disk, then use your external source control tools to commit/check-in them. The problem you noted is that your .sas programs are not accessed in EG through the local file system.  Rather, you access them through the SAS server.  With most source control systems, you work off of local copies of the files, then you commit or check them in to your central repository.  So, to use source control with EG, we recommend not saving the files through the SAS server, since source control systems do not work through the SAS server -- they require file system access.  Rather, your working copies should be accessible from your local file system (and opened from there in EG), then commited/checked-in to your central repository. (Note: It is possible to continue saving the files to the SAS server, then commit them from the host machine of the SAS server using your source control tools, but we definitely do not recommend this approach for a number of reasons... if multiple users are working on the same working copies of the files it will be difficult to see who actually made which changes (whoever commits the changes will "have made" the changes), users won't typically have access to the server machine to commit/check-in, etc.) ... View more

UPDATE: Whoops, I see Mark beat me to it.  Glad we had the same thing to say! As a test, Tech Support would likely have you try connecting to the metadata server from the same machine using the SAS Integration Technologies Configuration Wizard (located here: C:\Program Files\SASHome\x86\Integration Technologies\ITConfig2.exe).  Click Test SAS Servers, Enter a SAS server definition manually, select SAS Metadata Server, enter the machine name of the host where your metadata server is running (same as in the EG profile), change port to 8561 (or the appropriate port of your metadata server -- same as in EG profile), and enter the same credentials used in the EG profile, then click Test.  If you can't make a connection from SAS Integration Technologies Configuration Wizard using the same connection information, then you won't be able to in EG either (EG uses Integration Technologies to connect to servers).  Check to make sure you entered the correct host and port of your metadata server.  Also, make sure you can ping the metadata server host from the client host.  If you aren't able to resolve, I recommend opening a ticket with Tech Support. ... View more

Do you wish to use code or point-and-click Query Builder? Here is steps using Query Builder (point-and-click) with your sample data... Create data set from your data: data bills; format Bill_Date MONYY7.; informat Bill_Date MONYY7.; infile datalines; input Account Bill_Date Address; datalines; 1 Nov-2012 1 addr 1 Dec-2012 1 addr ... 3 Feb-2014 10 addr 3 Mar-2014 10 addr run; Run the Query Builder with very similar to the steps I supplied earlier... -Select all three variables -Select N function in the Summary column for the Bill_Date variable (Notice: It automatically groups by account and address.) Should look similar to: On the Filter tab, specify two filters: -Bill_Date between 1/1/2013 and 12/31/2013 -N_of_Bill_Date >= 12 It should look like: Run the Query Builder and the result should return the accounts that have 12 consecutive bills at the same address (one record in this case): Now you simply need to join this table with your original table to get the bills for that account: -start a new Query Builder on the original table (named BILLS in my case) -add the table that is the result of the first query (QUERY_FOR_BILLS) (The Query Builder will automatically detect a join, but confirm joining by Account by pressing the Join Tables button.) Run the query and you should end up with this final result (the 17 records from account 1): And your process flow should look something like this: Casey ... View more

Tom, It was great to see and talk to you as well!  I'm glad you like the new features and enhancements.  We will continue striving to improve! Casey ... View more

Here is how I accomplished what I believe you are asking using the point-and-click Query Builder... First, I created some simple (hopefully close to representative) data: data billing; format billdate date9.; informat billdate date9.; infile datalines dsd; input account billdate; datalines; 1,01JAN2013 1,01JAN2014 1,02JAN2014 2,01JAN2013 2,03JAN2014 3,04JAN2014 3,05JAN2014 4,06JAN2014 5,07JAN2014 run; Then, I ran the Query Builder... -selected the billdate and account variables -summarized the billdate variable with N (to get the count of the number of bills; notice it is automatically grouped by account) Looked like this: Then, on the Filter tab, I defined two filters... -where billdate is between 1/1/2014 and 12/31/2014 (since only interested in 2014 bills) -where N_of_billdate > 1 (you would use > 12, but for my sample data only looking for more than one bill) Looked like this: Then I ran the Query Builder and got the accounts with more than one bill in 2014: Of course, you'd have to tweak it for your data. ... View more

I would think Citrix Xenapp would have a way to configure file type associations, such that you could associate certain file types (ex. .egp in this case) on the client machine to a Citrix Xenapp published application (EG), but I can't confirm.  A quick Google search provided some hits that looks like there is a way: To associate published applications with file types - Citrix eDocs ... View more