Apache Subversion vs. Pragmatic Workbench (discontinued)

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.

Incentivized

Workbench Enterprise is consistent across devices and users so far. It works the same, and access is easy. I have a problem with its security. If you use an enterprise password to access databases, it's very easy to click the show password on the connection page and expose the enterprise password. You shouldn't allow users to use the same accounts to access the database because that means all users are sharing the same password.

Incentivized

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

Incentivized

• Querying is easy and quick.
• Updating tables is very easy.
• It gives us very accurate error messages.

Incentivized

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

Incentivized

• It has autocompleted, but I find it difficult to use or get to use.
• It doesn't automatically complete table names or field names.

Incentivized

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.

Our team does the support for us. Sometimes we see download related issues that can easily be fixed by our team. Most issues you will see with one user in your org will probably happen to others, so keep a log and track those issues. Then have a fix for them somewhere that everyone has access to. This will save you a lot of time troubleshooting.

Incentivized

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.

Incentivized

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

Incentivized

• I personally like Workbench Enterprise, and I can do everything I need to do using it.

Incentivized