Likelihood to Recommend It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
Read full review 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.
Read full review Pros Revision control done properly - you have end to end visibility of all changes in the project. Conflict resolution - visually highlighting the differences helps to track down the problem. Being open source and very popular. We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years. Rollbacks are made simple and easy to use. Read full review 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. Read full review Cons Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists. Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!) Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion. Read full review 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. Read full review Likelihood to Renew While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
Read full review Usability It's a good tool to have, but becomes expensive to buy a user license for each developer.
Read full review Support Rating They have a great community website where you can search for answers but are also very responsive when it comes to direct support.
Read full review Alternatives Considered Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but
Git is the future.
Read full review 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.
Read full review Return on Investment Subversion helps us feel secure in maintaining access to all of our product code, both current and historical. Being free and open source makes it an even better "investment". Read full review 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. Read full review ScreenShots