As organizations grow, their application and database scenarios can become more complex, and it becomes increasingly important for IT to standardize the deployments of these environments. Standardization not only reduces mistakes by ensuring that each deployment is done exactly the same way, but it decreases deployment time. Fortunately, solutions are available to assist with the process, such as GridApp's database automation management solution, Clarity 3.5, aimed at companies running Oracle, Oracle RAC (Real Application Clusters), and to a lesser degree, SQL Server.
Installing Clarity is fairly straightforward: Install the Clarity Manager management server and the repository database (if you're going to have one). Of course, you also must upload all of the software you're going to manage, be it Oracle, SQL Server, or RAC, as well as any patches you're going to push out.
The next step is to start adding servers to "grids" (these aren't performance grids, it's just the name GridApp uses for the top-level storage containers). Then install management agents on them by simply pushing them out from the Clarity server. Now you're ready to create your templates.
Templates are the basis for everything you'll do in Clarity. Configuring them is easy as they're XML-based, so it's really no problem to create any number with both dynamic and static options. This is a very powerful function, especially for RAC deployments, which are complex and fraught with potential pitfalls. Being able to specify that certain options get implemented with specific values is not only incredibly important, it's a huge time-saver.
Once I had my templates created, I was able to provision a primary instance of a new RAC cluster in just a few minutes via the management server UI. Provisioning the next node was even easier because Clarity is smart enough to know what can and can't be changed when you add a node to an existing cluster. Thus, some options are static no matter how you configured them in the template. As a result, anyone in the datacenter can easily add a node to the cluster: All you have to do is provide the name of the cluster, and everything else is done automatically.
Notably, Clarity can't provision SQL Server clusters, which is indicative of its relatively limited SQL support.
I was pleasantly surprised by how easy it was to add nodes. However, I have to criticize the fact that you must go through the wizard each time. You can't schedule deployments, and you can't run them unattended. Don't get me wrong; the time savings are still significant, it'd just be nice to have a one-click solution. Additionally, I don't like that you can't prevent someone from deploying Oracle or SQL Server on a managed box; Clarity will just tell you that it's been done after the fact.
Clarity's management server delivers some useful auditing capabilities, enabling an admin to see who has done what. I do wish it would let you monitor changes to the templates themselves, however, so you could tell who made a change if, for example, a deployment gets provisioned incorrectly. Unfortunately, templates are edited outside of the management server, so that's not possible currently. The management server UI also could use a makeover; it could benefit not only from some layout enhancements but improved graphics and color scheme as well.
Clarity maintains its value after the initial deployment, in that it can easily serve as your main patch deployment and management system. For Oracle, you can approve patches and push them out to servers very easily. I wish the solution could connect to the Oracle site and check for patches automatically. Currently you have to download the patches manually and upload them to Clarity, but once they're there, you're golden.
The patch management for SQL Server 2005 works the same way. Moreover, it allows you to see the patch levels of all managed servers, which is difficult to do using Microsoft's native tools. Unfortunately, it won't do patch management for SQL Server 2000.
Clarity's basic functionality is great, but the real question is how does it scale? Realistically, a single Clarity management server can scale to about 300 managed agents. The GUI gets a little thick after that, but being browser based, it's really not Clarity's fault. Other than that, you can't provision several boxes at once, so from that standpoint there's no difference between managing one server or 300.