In reply to Hari Rajan.

Hari,

Service Profiles are not to be considered a replacement for SQL Server Fail-Over Clustering. SQL Server Fail-Over Clustering should be your first choice for maintaining data integrity and redundancy.

That said, there are a few ways to accomplish your objectives:

You could develop an app that leverages Cisco UCS's XML API to automate the un-association/association of the Service Profile to the spare blade. While I cannot share it, I have built a C++ app that monitors a workload and should it become non-responsive, the app will speak to the XML API and instruct UCS to move the workload to a spare blade.

Another way would be to leverage our System Center integration to receive notifications based on the health of a server and launch a PowerShell script to do something similar to the functionality I describe above. System Center's Pro TIPS may be able to help here as well: http://technet.microsoft.com/en-us/library/hh882399.aspx

Finally, I must say that a simple manual process is still exponentially faster than what most companies are experiencing today on other hardware platforms.

I hope this helps,
Frank Cicalese