Turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings

Make SLX OLEDB Provider Cluster Friendly

Status: New
by Employee on ‎11-02-2009 10:36 AM
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.
Comments
by Gold Super Contributor RJLedger
on ‎11-02-2009 11:23 AM
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"
by Employee
on ‎11-03-2009 05:15 PM

Could you expand on the "also work inside of a Clustered Database environment"?  I'd like to know what your expectations are that would be additional to what you can do today.

 

Today, you can set your native connection (in the SLX Data Link Manager) to your Clustered Database environemnt, since it would have its Virtual Cluster name to use.

by Gold Super Contributor RJLedger
on ‎11-03-2009 05:35 PM
Phil, I think he means to install the back end (SalesLogix server) ON the cluster.
by Employee
on ‎11-03-2009 10:24 PM
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.
by Employee
on ‎11-23-2009 12:08 PM

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.

We want to hear your cool ideas for enhancing Saleslogix products and services. So add your own ideas or kudo (vote) on the ideas of others here! Watch the most valuable bubble to the top!

I have an idea! How do I get started?

One
Read our submission guidelines.

Two
Search for your idea. If you don't see it, submit a new one!

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

Four
Track 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!

Here is a quick list of the recent ideas for speedy browsing!
Labels