IBM Cognos is a full-featured business intelligence suite by IBM, designed for larger deployments. It comprises Query Studio, Reporting Studio, Analysis Studio and Event Studio, and Cognos Administration along with tools for Microsoft Office integration, full-text search, and dashboards.
$10
per month per user
SAS Enterprise Guide
Score 9.2 out of 10
N/A
SAS Enterprise Guide is a menu-driven, Windows GUI tool for SAS.
Well suited: Financial reporting - It can handle complex, pixel perfect, muti-page reports with scheduled delivery to stakeholders (like sales report by region on quarterly periodicity) Operational dashboard across departments - It can combine multiple data sources (ERP, CRM, excels etc) with filters, and embedded AI insights Less appropriate: Live dashboards - As stated earlier as well, IBM Cognos Analytics doesn't suit well for live dashboards or event driven data. For ex: live web traffic data or IOT device data, etc Data science - Although IBM Cognos Analytics is great tool for data exploration but it should not be used as a substitute for Python or R, which has edge over advanced modelling and stats based workflows like predictive modelling or clustering
SAS Enterprise Guide is good at taking various datasets and giving analyst/user ability to do some transformations without substantial amounts of code. Once the data is inside SAS, the memory of it is very efficient. Using SAS for data analysis can be helpful. It will give good statistics for you, and it has a robust set of functions that aid analysis.
IBM Cognos Analytics enables customer data segmentation, which is essential for marketing, improving and streamlining purchasing behavior and preferences. This helps companies create more targeted and effective marketing campaigns.
Our clients Through data analysis, we can identify and observe trends in the behavior of other clients, allowing us to anticipate needs and adjust strategies to avoid consequences.
Process time of data is a bit long. It depends on the size of your data and complexity of your project tree.
There is not enough online free training videos.
While working with the project tree sometimes the links between the modules are broken or the order for running the modules get mixed up. You should know your project tree by heart.
For an existing solution, renewing licenses does provide a good return on investment. Additionally, while rolling out scorecards and dashboards with little adhoc capabilities, to end users, cognos is very easily scalable. It also allows to create a solution that has a mix of OLAP and relational data-sources, which is a limitation with other tools. Synchronizing with existing security setup is easy too.
We have a strong user base (3500 users) that are highly utilizing this tool. Basic users are able to consume content within the applied security model. We have a set of advanced users that really push the limits of Cognos with Report and Query Studio. These users have created a lot of personal content and stored it in 'My Reports'. Users enjoy this flexibility.
It's not all bad, but I don't believe that an enterprise purchase of SAS is worth the expense considering the widely available set of tools in the data analytics space at the moment. In my company, it's a good tool because others use it. Otherwise, I wouldn't purchase a new set of it because it doesn't have some of the better analytical functions in it.
Reports can typically be viewed through any browser that can access the server, so the availability is ultimately up to what the company utilizing it is comfortable with allowing, though report development tends to be more picky about browsers and settings as mentioned above. It also has an optional iPad app and general mobile browsing support, but dashboards lack the mobile compatibility. What keeps it from getting a higher score is the desktop tools that are vital to the development process. The compatibility with only Windows when the server has a wide range of compatibility can be a real sore point for a company that outfits its employees exclusively with Mac or Linux machines. Of course, if they are planning on outsourcing the development anyways, it's a rather moot point
Overall no major complaints but it doesn't handle DMR (Dimensionally Modeled for Relational) very well. DMR modelling is a capability that IBM Cognos Framework Manager provides allowing you to specify dimensional information for relational metadata and allows for OLAP-style queries. However, the capability is not very efficient and, for example, if I'm using only 2 columns on a 20-column model, the software is not smart enough to exclude 18 columns and the query side gets progressively larger and larger until it's effectively unusable.
Why is their web application not working as fast as you think it should? They never know, and it is always a a bunch of shots in the dark to find out. Trying to download software from them is like trying to find a book at the library before computers were invented.
Although I use SAS support for information on functions, these are SAS related and haven't really come across anything that is specifically for SAS EG.
Onsite training provided by IBM Cognos was effective and as expected. They did not perform training with our data which was a bit difficult for our end-users.
The online courses they offer are thorough and presented in such a way that someone who isn't already familiar with the general design methodologies used in this field will be capable of making a good design. The training environments are provided as a fully self contained virtual machine with everything needed already to create the environments. We've had some persisting issues with the environments becoming unavailable, but support has been responsive when these issues arise and straightening them out for us
Make sure that any custom tables that you have, are built into your metadata packages. You can still access them via SQL queries in Cognos, but it is much easier to have them as a part of the available metadata packages.
I've not worked hands-on with the implementation team, but there were no escalations barring a few hiccups in the deployment due to change in requirement & adoption to our company's remote servers.
Power BI is stronger for quick ad-hoc analysis and dashboards, but IBM Cognos Analytics is better when consistency, precision, and mass distribution matter. Tableau is best for interactive analysis, while IBM Cognos Analytics is better for standardized, repeatable enterprise reporting. Sigma shines for customizable dashboards and drill-down analysis while IBM Cognos Analytics holds an edge in data discovery and visualization.
Why I prefer SAS EG: Data processing speed is much faster than that R Studio. It can load any amount of data and any type of data like structured or unstructured or semi-structured. Its output delivery system by which we have the output in PDF file makes it very comfortable to use and share that file to clients very easily. Inbuilt functions are very powerful and plentiful. Facility of writing macros makes it far away from its competitors.
The Cognos architecture is well suited for scalability. However, the architecture must be designed with scalability in mind from day one of the implementation. We recently upgraded from 10.1 to 10.2.1 and took the opportunity to revamp our architecture. It is now poised for future growth and scalability.
Positive (cost): SAS made a bundle that include unlimited usage of SAS/Enterprise Guide with a server solution. That by itself made the company save a lot of money by not having to pay individual licences anymore.
Positive (insight): Data analysts in business units often need to crunch data and they don't have access to ETL tools to do it. Having access to SAS/EG gives them that power.
Positive (time to market): Having the users develop components with SAS/EG allows for easier integration in a production environment (SAS batch job) as no code rework is required.
