Dundas BI is a business intelligence and data visualization software that includes customizable dashboards, reporting, and visual data analytics. Dundas BI can be integrated into users’ existing business applications and its visualization and reporting tools can be customized to their needs.
N/A
erwin Data Modeler
Score 8.9 out of 10
N/A
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.
For all the scenarios I have so far worked on or I am currently working on, Dundas BI has proved to be more than adequate and apt to handle all of those. It is a very easy-to-use tool with quick shortcuts enabling you to prepare ad-hoc reports or dashboards in a matter of minutes.
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.
Project organization from Development to Production, you get a production and development license but I think the best way to do it is with DEV and Prod project in the Production box. Use the development box for testing updates and really crazy things. With the Dev and Prod projects on the same box, you just publish from Dev to Prod and you are done. Users only have access to the Prod projects so no one can mess up what you are working on.
Security - If you have a hierarchy (subsidiaries, divisions, department, teams) and you want each group to see only their data, then Security hierarchies are for you!
Dependent filters! What's this you ask? Here is an example of how it can be used, in your company you have departments and who works for what department is in your database. You make a dashboard that has a department filter (only show these departments), a managers filter, and employee filter. Not every manager or employee is in multiple departments usually only one. With dependent filters you can say that the manager and employee filter are dependent on what is selected in the departments filter so when you go to filter them they only show the managers or employees that are part of that department, and you can even it do so employees are not only dependent on department but on manager as well. Then it gets even better as it can be done in reverse as well so when you select a manager then go to the department it only shows the departments he works for (there are better situations where this is more useful).
It is scriptable! From calculate columns, null replacements, button actions, load actions, hover over events there a way to do what you want.
They are constantly improving and listens to your suggestions.
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.
Not too many cons for how we use the application. It really is easy and powerful. Very powerful.
Licensing is one thing that could be looked into. It is simple, but a little confusing. For example, if I get a license today, but a new release comes out tomorrow, it seems that the license doesn't work with the new release. Maybe that is by design, but it would be nice to clearly understand.
We are still in the implementation phase, but so far we are finding it to be easy to use and learn. The eLearning courses that they have made available for free, as well as User Forums and other training videos have made even difficult concepts easier to understand.
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 bi-weekly calls with our Success Manager, as well as access to support as needed. Any question that I have had, multiple people have been willing and able to jump on a call to talk me through it, or send an email with the solution
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.
Per dollar spent, it offers the widest range of features of the tools that we evaluated. It offers lots of options for how to configure your environment, though they are not always intuitive to figure out. Having an ETL layer was a must have for us, as well as the ability to host to secure HIPAA compliance. It is not a replacement for ad hoc reporting, but does a great job of creating parameterized reports and dashboards that look great.
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.
