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
Microsoft BI (MSBI)
Score 8.7 out of 10
N/A
Microsoft BI is a business intelligence product used for data analysis and generating reports on server-based data. It features unlimited data analysis capacity with its reporting engine, SQL Server Reporting Services alongside ETL, master data management, and data cleansing.
$14
per month per user
Sigma
Score 8.2 out of 10
N/A
Sigma Computing headquartered in San Francisco provides a suite of data services such as code free data modeling, data search and explorating, and related BI and data visualization services.
IBM is a titan in BI innovation but has arduous competitors as I mentioned before. IBM has prestige in BI and the directors and managers know that. On the other hand, complexity is not the strategy of Cognos, that's why if you need big cubes of data, Tableau, and Microsoft BI …
I like the cloud native character and ease of deployment with Sigma and ThogthSpot, I also like the metadata modelling capabilities of Power BI. I prefer the ability of Cognos to create and publish a metadata model that provides both ad hoc access and managed reporting and …
Cognos Analytics provides wide range for reporting, data visualization, and self service analytics. Cognos has strong security and governance features. Sigma Computing is purely cloud native approach and has spreadsheet like interface and doesn't provide many customization …
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 …
Microsoft Power BI has a more user friendly interface and it is integrated very well with the other Microsoft products but IBM Cognos Analytics has a more advanced reporting and complex data analysis capabilities.
Cost wise, the above products are less expensive and offer tons more upfront, but you will pay for it on the back end. They have vendor limitations and their support mechanism was inline for what we wanted.
It was cost prohibitive to switch platforms we have a huge investment in our Cognos implementation. There was retooling costs for our resources training costs for our users as well as a million $ plus investment in licensing costs. We could have considered a move to the cloud …
There are a number of reporting systems, but these other systems are really data visualization systems that lack the ability deliver information through an enterprise on their own. IBM Cognos is well suited to be the delivery system for an enterprise's analytics and the …
MS BI: A lot of times we meet customers who are dealing with an MS BI maintenance nightmare and we try to ease their pain by implementing Cognos BI and their reporting and analysis system. Cognos BI is better than MS BI from ease of implementation to production support and …
Cognos has better functionality and it is easier to develop once the package is ready. On the other hand SSRS doesn't need a package, just a connection to DB.
IBM Cognos is a separate product but it allows us to connect to any databases and databases from Microsoft Analysis Services as well. This feature made me choose Cognos.
Each of the solutions has their pros and cons, but Microsoft's BI offerings provide the best "bang for the buck." Few solutions available offer the breadth of feature functionality in a single package, with BI and database generally being sold as separate offerings. However, …
We initially considered Google Analytics, but eventually decided against it due to the licensing terms and the associated software that we would need to incorporate. IBM Cognos is great at what it does, as long as you are trying to integrate with software that is on their …
Specific data displays are some of the strongest aspects of Microsoft BI when compared to alternate programs. It also does a superior job in compatibility with many programs, especially those from Microsoft. Since my company primarily uses Office 365 and other Microsoft …
Microsoft BI is mainly based on Microsoft SQL Server, so it is perfectly integrated. Many of the Microsoft BI components require using SQL Server as the database engine. Generally, the functionalities that are achieved when using SQL Server as a database engine are greater than …
One of the main reasons Microsoft BI was chosen by our company is because it is a reliable program. We tried different programs in the past (and currently also use other ones for certain reporting and analysis needs) but Microsoft BI was the least buggy out of our top choices.
-Tableau is clearly more cutting edge when it comes to data visualization and connecting to multiple data sources (support for MongoDB, Hadoop, etc). -Assuming your data is not that sophisticated, Microsoft BI is a great product. I would say its a good "all around" BI tool. It …
Much better than IBM Cognos. However, I prefer Tableau over Sigma due to its robust optionality. Sigma's only leg up on Tableau is its ease of use and speed of producing visuals and iterating tables.
Sigma Computing is significantly faster and more versatile than Data Studio integrations for marketing data. While it is less powerful than Tableau for data visualization, it is much easier to use due to its spread sheet like user interface. Microsoft BI is a middle ground but …
Sigma Computing was our top choice due to the ease of use of the platform for end users doing self-exploration of data. The structure of the platform for how datasets are created and access provisioned was much better than other products we considered. Sigma Computing may not …
Most legacy BI tools are just that--built in and for a time that has mostly passed. Each tool seems to have strengths in certain areas, but can be overly complex to take full advantage of and can make some of the most basic tasks difficult to discover and use. Sigma Computing …
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
Microsoft BI has a lot of features and is a very powerful tool, especially if you have folks on your team that know how to utilize all of its capabilities. To truly unlock all that it can do, it does require people to have a deep understanding of its capabilities. That's where the software really shines. If you are looking for a simpler, more basic reporting tool, there are other programs available that do not require such a steep learning curve.
We were able to set up client-facing embedded reports with ease and security. The interface is not difficult to learn, although we may not be aware of or lack the necessary expertise to utilize more advanced features that would likely benefit us.
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.
Sigma Computing does not allow custom ordering of pivot fields in pivot tables easily
Sigma Computing lacks functionality for creating tables or sections that dynamically adjust to the browser window's height while maintaining a fixed height textbox at the bottom
Sigma Computing does not provide straightforward options for formatting totals in tables, such as renaming 'Total' to 'Average', 'Team Total', etc
Sigma Computing does not support searching by individual tab names within a workbook
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.
Microsoft BI is fundamental to our suite of BI applications. That being said, Northcraft Analytics is focused on delighting our customers, so if the underlying factors of our decision change, we would choose to re-write our BI applications on a different stack. Luckily, mathematics are the fundamental IP of our technology... and is portable across all BI platforms for the foreseeable future.
Sigma has helped us a lot and has become an integral part of our daily workflow. It would be difficult to switch to another platform and have to rebuild the numerous metrics and performance reports that we have already established
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.
The Microsoft BI tools have great usability for both developers and end users alike. For developers familiar with Visual Studio, there is little learning curve. For those not, the single Visual Studio IDE means not having to learn separate tools for each component. For end-users, the web interface for SSRS is simple to navigate with intuitive controls. For ad-hoc analysis, Excel can connect directly to SSAS and provide a pivot table like experience which is familiar to many users. For database development, there is beginning to be some confusion, as there are now three tool choices (VS, SSMS, Azure Data Studio) for developers. I would like to see Azure Data Studio become the superset of SSMS and eventually supplant it.
It has a clean and modern interface. However, it is not completely intuitive. I think it would be better and easier to navigate with more Windows style drop down menus and/or tabls. There is a significant learning curve, but that may be due in part to the technical nature of this type of software tool.
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.
SQL Server Reporting Services (SSRS) can drag at times. We created two report servers and placed them under an F5 load balancer. This configuration has worked well. We have seen sluggish performance at times due to the Windows Firewall.
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.
MSBI natively has a site that allows you to vote on user enhancements and bug fixes. This allows the largest nagging issues to float to the top and the development team can prioritize accordingly. As mentioned earlier, the large community base of MSBI developers assist technical resources in handling technical questions.
They are very friendly and informative. They are quick in resolving our queries and help us understand very minute things as well. They are quick in creating feature tickets based on our custom requirements, and they would also create a bug ticket if there is any discrepancy and get that checked on time.
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
I have used on-line training from Microsoft and from Pragmatic Works. I would recommend Pragmatic Works as the best way to get up to speed quickly, and then use the Microsoft on-line training to deep dive into specific features that you need to get depth with.
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.
We are a consulting firm and as such our best resources are always billing on client projects. Our internal implementation has weaknesses, but that's true for any company like ours. My rating is based on the product's ease of implementation.
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.
We have used the built in ConnectWise Manager reports and custom reports. The reports provide static data. PowerBI shows us live data we can drill down into and easily adjust parameters. It's much more useful than a static PDF report.
With Looker, to be effective, a substantial amount of coding & modeling needs to happen in LookML. Being another language to learn, users have to context switch again from at a minimum either SQL or Python into LookML. The concept of being able to source control, code review, and deploy your models is a plus though.
Tableau is the gold standard for data visualization, no question. Power users will be able to create dazzling content that Sigma won't necessarily be able to easily match. However, since development usually happens via an extract, helping other users troubleshoot is an arduous process. Trying to re-do or un-do all the transformations and calculations that cause a certain number is very difficult.
With Sigma, all the queries happen directly against Snowflake and you can see the query logs. The data modeling happens right in a tabular, spreadsheet-like manner, so within only a few minutes, substantial transformations can happen, with visualizations just a few more clicks away.
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.
As a SaaS provider we see being able to provide self-service BI to our client users as a competitive advantage. In fact the MSSQL enabled BI is a contributing factor to many winning RFPs we have done for prospective client organisations.
However MSSQL BI requires extensive knowledge and skills to design and develop data warehouses & data models as a foundation to support business analysts and users to interrogate data effectively and efficiently. Often times we find having strong in-house MSSQL expertise is a bless.
Monitoring health of cloud platform has allowed the company to anticipate issues before they affect customers – Sigma prompted us building a canary monitoring process that provides customer container health.
Customer success has used an activity report to discover customers running runaway processes that they were unaware of, creating an alert to contact the customer and prevent an embarrassing situation.
Customer success uses the activity report to prompt conversations regarding increases or declines in behavior that led to increasing contract limits or addressing churn concerns.