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 …
In the same way as the "twin" software (Redgate SQL Compare), this software has always proved to be perfectly functional, simple, fast and intuitive and it is for this reason that no other alternative software has been evaluated at Redgate Data Compare. I agree that looking for …
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.
If you plan to use Redgate Data Compare to automate data change between tables or SCD or similar, this is not the software that is right for you, Data Compare is a software that performs simply (but in an optimal manner) the comparison of data between tables of different databases on different environments or clone or mirror databases even on the same environment or server. Once the data is compared, you can select or deselect each line you want to update and then have the data alignment script prepared for it.
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.
Simple and easy comparison of database 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.
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.
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.
In the same way as the "twin" software (Redgate SQL Compare), this software has always proved to be perfectly functional, simple, fast and intuitive and it is for this reason that no other alternative software has been evaluated at Redgate Data Compare. I agree that looking for other software is always useful and is probably a best practice in some cases, but I am also of the idea that if a software does what it really says, it makes no sense to change it.
It's reduced errors and bugs associated with deploying new application features and forgetting to apply required database changes (or incorrectly applying them).
It's made deploying new features a quicker task, eliminating the often laborious task of synchronizing data across databases.
These sometimes complex queries and operations can easily be performed by any developer and don't require the involvement of a database administrator to perform.
