ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
$1,470.40
one-time fee per user
Liquibase
Score 8.5 out of 10
Enterprise companies (1,001+ employees)
Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database change management into their process than low performers. Liquibase delivers DevOps for the database. Liquibase value proposition: Liquibase speeds up the development process. The…
$5,000
per year
Pricing
ER/Studio Data Architect
Liquibase
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
ER/Studio Data Architect
Liquibase
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
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.
Data Architect is well suited at organizations of all sizes. It is never too early or unnecessary to enforce proper modelling and design standards on data solutions, and this tool will help that greatly by providing an industry leading data modelling tool, ability to import ETL mappings for data lineage, enforcing and managing naming conventions through the naming convention tool, and publishing of data dictionaries through the report publisher. I was successfully able to build models, provide traceability, and document source to target with lineage throughout for both the business (by providing business definitions in the descriptions), and technical teams (by documenting ETL instructions in text fields) along with field level mapping (by creating "Attachments" representing data sources, tables, and fields) providing easy search capabilities using business friendly terms
Store versions of DB's and Schemas this is useful for every software developer company that works with Databases. Now days al the software use a DB and control those changes are a must. have the power to rollback safe has change the way that we work. This increase speed in development while increase the business confidence.
ER/Studio has the ability to provide consistent field names and data types through domains, which are templates. This provides a way to have consistent naming of common fields, like CreatedBy and the data types for the fields. They also have the ability to change all the fields that use that domain to a different data type.
ER/Studio provides the ability to create custom macros. These macros can be used to apply everything from standard fields based on domains to naming all constraints and indexes. I've also used a macro that comes with ER/Studio to spell check field and table names.
My favorite feature is the ability to compare your data model to databases for deployments of changes, and to other data models.
It can automate database deployment scripts, consistently deploy the same way in every environment, have rollbacks always prepared for every database change, and have all detailed info of deployments in one place
Liquibase's changelog files serve as a centralized hub for all database changes. This makes it easy for multiple developers to work on the same project without conflicts, enhancing collaboration and reducing errors
ER\Studio licensing can be cumbersome and upgrading from one version to another usually takes several phone calls and emails to the licensing group to get the update installed and running.
The repository can be slow when the model count gets larger. By large I mean 20 to 30 models.
A nice feature that I would like to see is table comments be displayed on the model along with the attributes. Currently you have to choose between the two.
Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
Liquibase should rollback the if any one of the changes fails.
We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.
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.
Liquibase's customer support is at the top of my list of all vendors I've ever worked with over my 12 years of experience. They work directly with you to be successful, and response time is second to none. Liquibase is committed to getting customers up and running and - more importantly - successful in their organization and becoming champions of the product.
Liquibase makes it easy to integrate into CI/CD pipelines, keeping the database and code in sync. The switch from one database management system to another is made easier by modeling the structure of the database in DBMS-independent XML rather than SQL. A user-friendly web console gives you a complete picture of the database landscape by showing you which environments have received a particular changeset.
ER/Studio has had a positive impact on my project as we can develop the data model and have a clear understanding of business needs before we continue with the development phase.
