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.
User interface is easy to use, and in some ways better than Toad. The left hand side shows all databases, and you can drill down to instance, storage, schemas, tablespaces, and performance views. The right hand side displays the details of the selected object.
This is the best tool if you want to manage multiple RDBMS platforms in a single tool using the same familiar interface. Other third party tools can do it also, but it's not nearly as integrated as this, and may require additional plug-ins installed. DBArtisan excels at this, and can perform cross-platform data migrations easily.
It has different DB analysts, which can help diagnose issues with performance, optimize storage, detect fragmentation, and plan for capacity growth. For almost any action you want to take, you can generate the DDL for preview, and/or schedule it to run at a specific time.
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.
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.
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.
It has a positive ROI on our organization. It's better than OEM and SQL Developer. Although the license could be expensive, it is perfect for large organizations, especially with multiple RDBMS platforms.
Most features are redundant between DBArtisan and Toad. I would not recommend using both if you already own one of them. Just download the trial for the one you're not using, and see what works best for your organization.
DBArtisan is great for DBAs and would be my personal preference. Toad is good for developers and DBAs alike but I feel like sometimes the interface is too busy and too clumsy to use.
