Interesting...you're moving to an environment very similar to the one that I supported for many years. To me, there are two big advantages I hope you'll see from moving to the new SAS environment.
First, Enterprise Guide connecting to SAS on a server gives you the user interface on your PC, but with the heavy lifting done on the server. Make sure that there is a very fast connection between your SAS server and your SQL Server environment.
Second, I promise that the SAS ETL, BI, and data management tools are phenomenal. I've specialized in them for twenty years now. I know that it's a pain to learn new stuff (I'm working on a Python project, and believe me, I'm suffering!), but I think you'll find it's effective for your needs.
If something seems wrong, or doesn't make any sense, post to this forum. There's lots of smart people on it!
Tom
Yes, but there's one big advantage...this is a volunteer project, and unfortunately there's no money to pay for SAS! 😞
So I'm doing the best I can with Python. To be honest, I'm finding it very interesting, and in many ways complimentary to SAS.
If we EVER get to meet up at SGF I'll tell you all about my experiences!
Best,
Tom
@TomKari wrote:
If we EVER get to meet up at SGF I'll tell you all about my experiences!
Best,
Tom
Sadly, this would be 2022 in San Diego at the earliest. Or you set up a Webex for us 😉
@Reeza wrote:
SuperUsers virtual drinks?
I'm all for it. During the COVID lockdown, we had a "virtual department beer" one time via Webex.
Glad to hear you made it this far! Like every other high-end product these days, SAS has multiple ways to import .csv files.
1. Using the "File | Import Data" dialogue in Enterprise Guide. In your case, DON'T use this, as it wants to examine the data on your local PC, and of course your data is on the server. This is a great option if you have a small dataset on your PC.
2. SAS has a software tool called "PROC IMPORT" which will bring data from a variety of formats into SAS. I was able to import a .csv version of the sashelp.cars dataset using this syntax:
proc import datafile="C:\ddd\cars.csv" out=cars dbms=csv;
run;
One nice thing about this option is it prints in the log the SAS code that it generates, so you can grab it and tailor it to your needs.
I suggest you give that code a try, and see what you think.
3. Just write plain old SAS code. This is my option of choice, since i) I've been around SAS since before .csv files existed, or PROC IMPORT or Enterprise Guide, for that matter, and ii) it gives me exquisite control over what's happening with my data. Comparing with the massive code generated by PROC IMPORT, I can pull in my .csv of the sashelp cars dataset with just
data work.cars;
length Make $13 Model $39 Type $6 Origin $6 DriveTrain $5 MSRP 8 Invoice 8 Engine_Size 8 Cylinders 8 Horsepower 8 MPG_City 8 MPG_Highway 8 Weight 8 Wheelbase 8;
infile "C:\Users\Tom\Desktop\cars.csv" lrecl=32767 dsd firstobs=2;
input Make Model Type Origin DriveTrain MSRP Invoice Engine_Size Cylinders Horsepower MPG_City MPG_Highway Weight Wheelbase;
run;
I know I'm kind of shoving a firehose up your nose and turning it on, it's a lot to learn. Ponder on and read about these, and come back with questions. I'm not going to be happy until you tell me you love SAS.
Tom
Re: use SAS as a relational engine:
Yes, you can, but (IMO) you shouldn't. While you will keep your base tables in a more or less normalized structure, don't waste time to set up integrity rules and constraints. That has already been done in the source DBMS, and the data you get will reflect this.
Re: reporting/presentation tool
Yes, yes, yes! Although you will find that SAS SQL misses some (or a lot) of the options provided in the SQL dialect you are used to, all the other tools (DATA and PROCEDURE steps) are much more powerful for data warehousing purposes than MS SQL and its brethren can ever be.
For reporting, your prime partners will be the DATA step for preparation, and the SUMMARY, TABULATE and REPORT procedures coupled with ODS (the Output Delivery System).
Since you seem to operate in an environment that is not so much different than what I am working in, here some assumptions I make:
To further help us to help you on your path, it will be very useful if you share some information about your SAS setup. We already know that you have a client/server setup with UNIX on the backend; what is available there on top (Web Report Studio, Stored Processes, OLAP), and which SAS modules are licensed?
Run a PROC SETINIT to see the license; if you want, post the log, but discard all site-specific information, keep only the list of modules.
What would I suggest to study next?
The most powerful tool for data preparation is the DATA step; I suggest to start here:
and here:
For the Procedures, I suggest Base SAS Procedures
Feel free to ask "How do I do this in SAS?" You will need a lot of pointers at first for this kind of question
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.