How to keep my application data written registry keys will be available to other nodes in a cluster when they become online in sql server2005? (I need to update registry keys to standby server when fail over occurs)
How to keep my application data written registry keys will be available to other nodes in a cluster when they become online in sql server2005? (I need to update registry keys to standby server when fail over occurs)
I'm not sure how writing registry keys from an application has much to do with SQL Server, seeing as you don't really provide any information. However, you should be using the cluster registry:
http://msdn.microsoft.com/en-us/library/aa369128(VS.85).aspx
However, it's pretty clear that MS don't really want you using the cluster registry, so it might be worth trying to explain more about what you want and why. It seems to me that the best place to store information would be the database.
You could create routines that keep the database and Registry synchronized. They would be very specific to your environment and application. The basic process logic could follow along these lines:
Have SQL parse the Registry for the application every 10 minutes, every hour or once a day\week\month, depending on your application's volatility, and store the information in a dB.
On SQL startup have a routine that writes the info stored in the dB into the Registry.
This would have your now active node's Registry holding the last known state from the previous node.
No one has followed this question yet.