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 Access
Score 7.7 out of 10
N/A
Microsoft Access is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software-development tools.
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 …
Report Writer was innovative in its day but it was very basic. It was good at accessing multiple data points but it was weak in creating formulas and I don't think you could get graphs out of it.
Excel is very good even today. You can really manipulate data and create pretty …
It stacks up well to Crystal Reporting because it does give you a more generic feel of having a real business object solution. We selected Microsoft Access because it is intuitive enough for our end users and it does give them their own personal workspace to achieve their goal …
In comparison to Cognos and SAP Business Objects I would say access has a lot more flexibility. This can be both good and bad depending on the type of user.
Our first and most basic scenario was to automatize the creation and publication/sharing of business reports that used to be created manually by employees throughout our organization. Using Cognos for that first use case worked well. The advanced analytics functionalities we used on the aggregated data were also as expected. However, the user interface is not always intuitive, and there is a steep learning curve, so I would recommend Cognos only to large organizations where there is a need for the most advanced functionalities (AI analysis/prediction).
Microsoft Access can be easily implemented with training. It doesn't require expert level skill for basic reporting functions - but can be scaled to a complex database with sophisticated users. Its appropriate to consider if excel needs to be used to create reports, or if there are data entry needs - with corresponding reports.
Sometimes there might be performance issues when dealing with large and complex data.
Although IBM provides full documentation but sometimes it's difficult to find answers to questions and connect with their customer support.
It relies on external tools for data cleaning, transformation and also for some integration tasks. It can also improve on providing wider range of data sources for integration.
Microsoft Access has not really changed at all for several years. It might be nice to see some upgrades and changes.
The help info is often not helpful. Need more tutorials for Microsoft Access to show how to do specific things.
Be careful naming objects such as tables, forms, etc. Names that are too long can get cut off in dialog boxes to choose a table, form, report, etc. So, I wish they would have resizable dialog boxes to allow you to see objects with long names.
I wish it could show me objects that are not in use in the database for current queries, tables, reports, forms, and macros. That way unused objects can be deleted without worrying about losing a report or query because you deleted the underlying object.
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.
I and the rest of my team will renew our Microsoft Access in the future because we use and maintain many different applications and databases created using Microsoft Access so we will need to maintain them in the future. Additionally, it is a standard at our place of work so it is at $0 cost to us to use. Another reason for renewing Microsoft Access is that we just don' t have the resources needed to extend into a network of users so we need to remain a single-desktop application at this time.
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.
Microsoft Access is easy to use. It is compatible with spreadsheets. It is a very good data management tool. There is scope to save a large amount of data in one place. For using this database, one does not need much training, can be shared among multiple users. This database has to sort and filtering features which seem to be very useful.
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.
While I have never contacted Microsoft directly for product support, for some reason there's a real prejudice against MS Access among most IT support professionals. They are usually discouraging when it comes to using MS Access. Most of this is due to their lack of understanding of MS Access and how it can improve one's productivity. If Microsoft invested more resources towards enhancing and promoting the use of MS Access then maybe things would be different.
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.
In the past Management had used Excel and Workiva capabilities to create the reporting dashboards that were being used to make decisions. Since switching to IBM Cognos Analytics the Company has been much more efficient and decision making has been streamlined. IBM Cognos Analytics was chosen due to its reputation and data visualization capabilities and neither have been wrong.
Crystal is easier for report writing, but isn't a database solution. Salesforce is lovely, but much more expensive than an old copy of Microsoft Office. For a small budget, [Microsoft] Access was really the only viable option. I only wish it was easier to write complex reports.
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.
