ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
N/A
Sparx Systems Enterprise Architect
Score 8.3 out of 10
N/A
Enterprise Architect is the flagship architecture management platform from global, Australian-headquartered company Sparx Systems.
$229
per license
Pricing
ER/Studio Data Architect
Sparx Systems Enterprise Architect
Editions & Modules
No answers on this topic
Professional
$229
per license
Corporate
$299
per license
Unified
$499
per license
Ultimate
$699
per license
Offerings
Pricing Offerings
ER/Studio Data Architect
Sparx Systems Enterprise Architect
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Pricing for new customers only, first year maintenance included. Maintenance includes access to technical support and product updates for the defined period of the agreement.
You need to have a Sparx EA go to person to help socialize the tool and ensure it is properly used (but again, this is true for most tools). IF a company is looking for a tool they can just buy an have people use they should stick to Visio because any true modeling tool requires expertise.
In an environment where you do not have a highly trained group of architects who are familiar with all the standards and strategies of modeling, Sparx EA , more than most tools, allows you to wrap user friendly menus,and windows around it to make it easier to use.
ER/Studio is great for dividing logical and physical design. A logical model can be used with different physical platforms.
Studio can a useful macro capability that allows me to apply the naming standards across the model with ease and consistency.
ER/Studio does a very good job at comparing the model with the actual database and generating DDL scripts for production deployments.
ER/Studio has an excellent reporting and model publishing capabilities allowing me to produce models in the HTML format and publish them for the team as needed.
Relationships are a bit on the weaker side. Many times I found orphaned relationships that I could not get rid of, or additional columns that were automatically created during the push to the physical model that appear to be due to key constraint bugs
There are a lot of bugs introduced when merging keys. I tend to model 2 tables for example logically, establish the relationship, and then merge the additional key column that is automatically created when establishing the relationship. This sometimes causes downstream issues with the physical model (creating duplicate columns with _1 appended)
Meta-data could be improved. I find it hard to keep descriptions and other meta information clean when copying and pasting from other sources due to formatting tags being introduced on each object (font, size, color, etc.). The attachment feature comes in handy, however I am looking for the ability to cleanly document and map multiple sources to a single target while providing searchability and traceability
I can call or email support and both get quick turn around. The only issue is they are on the west coast (US) and have a west coast work schedule and I'm on the East coast.
ER Studio Data Architect is a global leader in the data modelling space and most other solutions that have support for third party data models include support for ER Studio Data Architect file formats. Many of the features are a bit more intuitive than the competitors and several of our vendors were already using Data Architect themselves which helped solidify the choice.
BiZZdesign represents a different new concept to enterprise architecture, its gravity center is not technical modelling, but rather a view on capturing the whole end-user experience or customer journey. It also allows to grasp areas as internal company capabilities, required for adoption/changes and operation of the solution, uses the same Archimate modelling language. This solution is in my opinion a new generation enabling to not only design the solutions, but also manage the whole application portfolio with respect to capabilities and requirement parameters.
Using ER\Studio to create models and eventually the actual database schema allows for a picture that is understandable to the customer and saves significant time writing DDL to create the database objects (tables, indexes, relationships, constraints...)
A nice customer interface tool so you can create a web based interface to the metadata for a particular design.
The tool also supports sub-models so you can break a large project into smaller parts, I find this feature very helpful.