We can connect to Amazon Red**bleep** using "SAS/ACCESS Interface to ODBC" as well as "SAS/ACCESS Interface to Amazon Redshift".
We have "SAS/ACCESS Interface to ODBC" in our SAS installation.
What are extra benefits of "SAS/ACCESS Interface to Amazon Redshift" over "SAS/ACCESS Interface to ODBC" ?
If you go down the SAS/ACCESS Interface to ODBC route you need to procure an ODBC driver manager, and procure an ODBC driver from somewhere. You then need to manage relationships with multiple vendors in the event issues arise and you need technical support.
The biggest advantage in my opinion with SAS/ACCESS Interface to Amazon Redshift is its a "batteries included" package. SAS provides everything you need, therefore you get access to a one stop shop for technical support for the SAS end.
From the usage point of view - it is significantly simpler to manage loading data into Amazon Redshift using the bulk load options available with SAS/ACCESS Interface to Redshift. The SAS/ACCESS Interface to Redshift access engine also provides a facility to enable encryption of data in S3 as its loaded in.
For more info about this check this link.
https://go.documentation.sas.com/?docsetId=acreldb&docsetTarget=n16eh98vroso8jn11e5z8ztvb4ez.htm&doc...
Check out these links to the documentation to understand the differences:
Redshift:
ODBC:
SAS/ACCESS to ODBC is a generic interface that will connect to any ODBC-compliant database. I use it to access SQL Server and Oracle. It's a whole lot more flexible and cheaper to have one product for multiple databases.
SAS/ACCESS Interface to Amazon Redshift is designed specifically for this database only. That means it will support features that perhaps ODBC doesn't.
Which is best for you depends on your requirements. If you don't use the database-specific enhancements in the Redshift interface then the ODBC alternative is a good choice.
Why there is extra cost for SAS/ACCESS Interface to Amazon Redshift?
What are the extra features which are present in SAS/ACCESS Interface to Amazon Redshift?
We have product SAS/ACCESS Interface to ODBC. There is will be one more component to be introduced in out environment "Amazon Redshift". So if we get SAS/ACCESS Interface to Amazon Redshift, what are the extra features which we will get?
If you go down the SAS/ACCESS Interface to ODBC route you need to procure an ODBC driver manager, and procure an ODBC driver from somewhere. You then need to manage relationships with multiple vendors in the event issues arise and you need technical support.
The biggest advantage in my opinion with SAS/ACCESS Interface to Amazon Redshift is its a "batteries included" package. SAS provides everything you need, therefore you get access to a one stop shop for technical support for the SAS end.
From the usage point of view - it is significantly simpler to manage loading data into Amazon Redshift using the bulk load options available with SAS/ACCESS Interface to Redshift. The SAS/ACCESS Interface to Redshift access engine also provides a facility to enable encryption of data in S3 as its loaded in.
For more info about this check this link.
https://go.documentation.sas.com/?docsetId=acreldb&docsetTarget=n16eh98vroso8jn11e5z8ztvb4ez.htm&doc...
Thank you. I am good with this explanation.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.