Make SLX OLEDB Provider Cluster Friendly

I would love to see this feature in SalesLogix where the OLE DB provider is able to detect a database failure and shift the connection to a back up serve, and also work inside of a Clustered Database environment.

This is a request from out customers I find happening ALL the time. many people have moved to SQL Server (Active/Passive) cluster(s) for max reliability and uptime. The weak link here is the "provider"

phil yes i am aware that today we could set it in a clustered database environment using the SQL Native Client, but the point is the SalesLogix OLEDB provider, in the event of failure to connect to the virtual cluster shift to another back end where there is high availability, and yes RJ is correct i meant install the back end on the cluster.

In Active/Passive failover cluster - the main impediment here is when you set up your connection, it automatically writes the SLX Server's machine name to SYSTEMINFO.PINGSERVER.

You could manually update the SYSTEMINFO.PINGSERVER field to be the virtual machine name of your cluster, so when the failover happens to the 2nd node, you don't have to re-setup the connection string.

Depending on how you setup your failover node, you may need to hook into it becoming the primary node & start up services. I believe I've seen posts in the old newsgroups about BP/Customers doing this today.

Three
Provide feedback on the ideas of others by voting with kudos and adding comments.
For more information about using ideas, read this thread.

FourTrack
your ideas and those you like. Once you've posted or kudoed and idea,
subscribe to be notified via email of the latest updates to the idea.
From within the idea, click "Idea Options" which appears above the idea title
and choose, "Subscribe to this idea".

Be sure to check back from time to time to see new ideas and status updates!