erwin Data Modeler by Quest is a data modeling tool used to find, visualize, design, deploy and standardize high-quality enterprise data assets. It can discover and document any data from anywhere for consistency, clarity and artifact reuse across large-scale data integration, master data management, metadata management, Big Data, business intelligence and analytics initiatives, accomplishing this whil esupporting data governance and intelligence efforts.
N/A
IBM Cognos Analytics
Score 7.5 out of 10
N/A
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.
$11.25
per month per user
SAP PowerDesigner
Score 8.0 out of 10
N/A
SAP PowerDesigner (formerly from Sybase) is an enterprise data architecture modeling tool, used to Build a blueprint of the current enterprise architecture and visualize the impact of change before it happens.
Oracle SQL Developer Data Modeler : Unfortunately this tool only supports Oracle Databases as a target database, but has many features similar to SAP Sybase PowerDesigner. erwin Data Modeler: Has some issues when switching from Conceptual Model to Physical Model, Impact …
Vice President, Chief Architect, Development Manager and Software Engineer
Chose SAP PowerDesigner
The version of ErWin we had didn't support the repository for document sharing and data dictionary sharing. Our version of PD does so we were able to leverage that and have a central repository that is shared among the team members. That really helped to give us consistency …
I have had a chance to use few other data modeling tools from Quest and Oracle, but I am most comfortable using erwin Data Modeler. They understand your data modeling needs and have designed the software to give you a feeling of completeness when you are designing a data model.
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
SAP PowerDesigner allows our team of data modelers to work and collaborate from a single repository and single data dictionary. This helps enforce consistency as data elements are referenced in other objects. Prior to our use of PD, we might have an element named "ppt" in one table, "participant" in another table and "part" in a third table. By forcing everything to be used from the data dictionary, we avoid these situations because everyone has to go to the dictionary. And we are able to easily do peer reviews on models before they are released because we are collaborating through the use of the repository.
Reverse Engineering: I love the way we can import an SQL file containing schema meta data and generate ER diagram out of it. This is specifically useful if you are implementing erwin Data Modeler for an existing database.
Forward Engineering: We use this feature very frequently. Where we do database changes in our physical and logical data models and then generate deployment scripts for the changes made.
Physical vs Logical Models: I like to have my database model split into physical and logical models and at the same time still linked to each other. Any changes you make to logical model or physical model shows up in the other.
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.
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 had a lot of experience using erwin Data Modeler for designing data models. I think it's pretty intuitive and easy to use. It has enough features to represent your database requirements in form of a model.
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.
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.
CA customer support and our account manager have been able to support us with any issues that we have had, from managing our serial keys to issues we logged tickets to resolve. There are aspects of key management that have made it difficult over the years but support usually has worked with us.
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.
We did have to reach out to support to learn how to properly utilize the repository feature and share the data model across many developers. Support was able to help us get this set up correctly. The downside was it took us several weeks before we gave up and contacted support. We should have done that earlier. I would say, however, the documentation wasn't clear on how to do this. So support was a great big help!
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.
Not listed, but I've only used alternatives built into something like the Squirrel SQL editor. That one is semi-functional but lacking many features and, in some instances, just plain wrong. The only pro there is that it's freely available and works over ODBC. I've tried some of the other free ones like Creately but didn't have much success.
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.
Oracle SQL Developer Data Modeler : Unfortunately this tool only supports Oracle Databases as a target database, but has many features similar to SAP Sybase PowerDesigner. erwin Data Modeler: Has some issues when switching from Conceptual Model to Physical Model, Impact Analysis, and formatting copy and pasting. Vertabelo: Only supports online models and from a governance perspective, it is impossible for me to connect my target database with an online application because of company policy and regulation requirements.
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.