We have been looking at the options to add additional graph types to our Flash Graph Portlet.
We would prefer to OEM something as it will give us a better long term strategy.
In researching options I found this Interesting blog post 28 Rich Data Visualization Tools.
Some we had already found some we hadn’t.
Still no Google Motion Chart options (aka SAS JMP chart), which I really want to include as a graphing option.
Well finally got confirmation that SPM 5.1/9.2 (now known as StM 5.1) has been released.
Doco is available on the SAS Support site here:
http://support.sas.com/documentation/solutions/performmanagement/stm/index.html
You will need to email your friendly SAS Support team for a password (only if you have a SPM license though)
I have read a few “how to” and “case Study” books on Data Warehousing over the last few years, and they all pretty much state if the quality of your data is rubbish, then the success of your Data Warehouse will be limited.
However it is often difficult to get an organisation to rectify all the Data Quality issues, before they embark on delivering reports and information to the business users who need it.
One of the interesting sessions at next years SAS Users Conference in New Zealand is by Zeeman van der Merwe who is talking about the work he is doing at ACC. I had the pleasure of meeting Zeeman a while ago and to talk to him about his project and he is definitely taking the recommended approach of sponsorship from the top and covering areas such as Data Governance, Data Stewardship and Data Quality reporting.
One of the Data Warehouse projects we are working on has a sister project dealing with Data Quality. It is fair to say we that we have yet to get the organisation to fully understand the impact data quality has on the business and the necessity to rectify the issues. Everybody does of course agree there are a lot of issues with the quality of the data which is a good start.
I always remember in my presales days at SAS the words customers always uttered “yes we have major data quality issues” shortly followed by “but we don’t have any money to pay to fix them”.
Anyway on this project we are lucky enough to have SAS Enterprise Data Integration Server at our beck and call and so have the ability to use Dataflux on the Warehouse data. So we have done a number of tactical Data Discovery and Data Validation pieces of works.
So far we have completed:
The Phone Number validation was the first one we did and we picked it as it was a discrete piece of work we could time bound, while we worked through the process to use Dataflux. We are now looking to close the loop by updating the augmented phone number data Dataflux produced inot the source system, and changing the business rules in the source system to rectify some data entry issues we identified.
I really recommend the idea of picking something small to start out with.
We are now looking at how we productionise the Data Quality routines into out standard Data Warehouse load and reporting processes. So far the options (in 9.1.3) look like:
Interesting thing to note is that in SAS 9.2 the Dataflux Integration Server component is bundled in eDI so you can just deploy the Dataflux Architect jobs and run them in your Warehouses standard process flows.
We still havent decided whihc option will work the best, but are thinking it is going to be the DI Studio option in the interim as consistency and stability of loads is one of our major focuses.
I have to say I love Dataflux and all that it does (I even believe the Dataflux team now have a stringer presence in the development of SAS Data Integration Server under the “Project Unity” banner).
I note that Dataflux jumped to the top of the Gartner Magic Quadrant in 2009. I always struggle to find this when I need them, so here are the Data Quality ones for 2008 and 2009.
Gartner 2008 Data Quality Magic Quadrant
Gartner 2009 Data Quality Magic Quadrant
Technologyevaluation.com sent me an email inviting me to use an online BI evaluation capability to see which BI vendor best meet my needs.
All the standard vendors (i.e SAP/BO, Oracle, Microsoft) are there but SAS is prominent in the fact that it is missing. Even more so when there are a number of small BI Vendors in the list (Yellowfon, Oco) I have never heard of.
(You will need to register)
Also interesting to note there are a number of Software as a Service (SaaS) offerings included.
Well course is over and I passed, so wahoo for me!
I am blogging all my tweets from the course so it is easier for me to search them in the future.
Enterprise Guide 4.2 and Office Addin 4.2 now have the ability to access OLAP cubes that are not registered in SAS Metadata.
Effectively this allows you to use the SAS tools to access non SAS cubes (assuming you have the OLEDB connector installed)
These are called Private OLAP Servers.
Following extract from 051-2009: What’s New in SAS® Add-In 4.2 for Microsoft Office explains it well.
PRIVATE OLAP SERVERS
Also new in 4.2 of the SAS add-in is the ability to define private OLAP servers. A private OLAP server is a direct connection to an OLAP server, rather than choosing one that is defined in metadata. The SAS Add-In for Microsoft Office now supports connecting to third-party OLAP providers, such as Microsoft Analysis Services or SAP BW, or any other vendor that defines an OLE DB compatible provider.
This is useful for users who have already invested in an OLE DB provider for OLAP. Now it is possible to use SAS to view and analyze that data. In SAS Add-In 2.1 for Microsoft Office, this was not allowed; the SAS add-in was able to connect to only a metadata-defined OLAP provider.
Once the user has opened the cube into the PivotTable, it works the same as any other PivotTable. The user has the full breadth of functionality available to them, such as drill-through, and adding calculated measures and members.
SAS 9.2 now has the concept of External Identities against a user or group.
The following is an extract of the online help:
Recent Comments