ER/Studio Data Architect vs. Redgate SQL Toolbelt Essentials

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

Incentivized

We use SQL Compare to troubleshoot performance problems quite a bit since our data model is more like a template and not everything is 100% in sync and customization occurs between different client databases. We continually get pulled into performance issues and the developers will say Client A is performing different than Client B, why? Using SQL Compare, we usually find that one client was tuned and had indexes altered or added that weren't deployed to all clients or other objects weren't deployed correctly during the release. On the other hand, since our data model practices allow client databases to drift I tried to create a new golden image by trying to compare multiple databases based on the same data model and found it to be a very difficult process to complete using SQL Compare. SQL Compare gave me too much information and doesn't allow enough filtering to eliminate a lot of the noise.

Incentivized

• 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.

Incentivized

• Simple and easy comparison of database schemas and data. Differences can be copied or synced from one database to another with a click of a button.
• You can save "projects" so that you can easily rerun a previous comparison whenever you need to.
• It has a very simple, easy to learn interface. I've never needed to read any documentation or watch any tutorials in order to figure out how to do something.

Incentivized

• 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.

Incentivized

• Pricing.... I wish there was an inexpensive developer version I could buy for myself.
• Portability.... I would like to use it from a flash drive so I can use it where ever I am asked to work.
• Unbundled.... This may be available already but I dont' recall I can buy it cheaply as a stand-alone product. Its only part of the bundle - cost effectively.

Incentivized

It's a good tool to have, but becomes expensive to buy a user license for each developer.

Incentivized

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.

Incentivized

They have a great community website where you can search for answers but are also very responsive when it comes to direct support.

Incentivized

ER/Studio is the most mature, reach in features and quality and therefore useful. Unfortunately, it lacks compatibility with AWS Redshift.

Incentivized

I've used Visual Studio Database Projects for this type of work in the past with some success, but Redgate SQL Compare is faster, more transparent, and simply easier to use. Faster is self explanatory. More transparent, means that it's much easier to set up your desired options for schema change deployment scripts. Easier to use, It's really dead simple. Start a project, connect your source, connect destination, click compare.

Incentivized

• 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.

Incentivized

• Makes deployment fairly simple. Cutting our deployment time down.
• With the SDK, we can customize our deployment process very quickly and easily.
• History is not great, it does create scripts you can go back and see but it would be nice to have a quicker version view by object to save time.

Incentivized