The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
SLX 6.2 and Clustered SQL Servers
Posted: 17 Apr 06 5:38 PM
|
fiogf49gjkf0d My company is about to implement clustered SQL servers. We have SLX 6.2.3.
Has anyone out there had experience with SLX on a cluster server environment? Can the OLEDB provider handle being pointed at the "virtual" machine name or IP? Any gotchas to watch out for? Is clustering even possible with SLX? Confused minds want to know!  |
|
|
|
Re: SLX 6.2 and Clustered SQL Servers
Posted: 18 Apr 06 1:08 AM
|
fiogf49gjkf0d I am going to have to dig out my notes but wanted to give you a quick answer. I would recommend pulling the SLX service and putting that over on a seperate box. If I recall you can get SalesLogix to behave in a clustered environment but the bottom line we ran into was why bother. You are spending the money on clustering (the extra server, the extra cost of SQL enterprise) so why not leave the SQL box to be SQL and put the SalesLogix provider on a seperate apps server? This just makes work with the system easier, in my opinion.
Ted |
|
|
|
Re: SLX 6.2 and Clustered SQL Servers
Posted: 18 Apr 06 3:41 AM
|
fiogf49gjkf0d I have to agree with Ted. We have a SQL clustered environment for our SalesLogix system. Originally we had the SLX server on the cluster (Passive / Active steup), with all clients pointing to a VIP to access the SalesLogix service and OLEDB provider. This set-up did not present any problems per-se, but as we started to move BizTalk and other databases on to the cluster it was felt that it would be a more efficient to have the SalesLogix server on a seperate box and leave the cluster to SQL server. So, in short. You can run your Saleslogix system on a clustered environment with no problems, but it's going to be better in the long run to migrate it to a seperate box. |
|
|
|
Re: SLX 6.2 and Clustered SQL Servers
Posted: 19 Apr 06 7:56 AM
|
fiogf49gjkf0d I have a customer who runs SalesLogix 6.2.2 on a Clustered SQL Server in a SAN environment. Everything works great, the trick to it is to have another SQL Server DB setup by itself, then install the SLX OLEDBProvider on that machine. Port a copy of the Database onto the Clustered SQL Server environment and point the provider to the new environment. You have to back end the SystemInfo table to put the SVS ID of the Clustered server in the ping field. But, this system has been working fine for a year now and it is an intensive remote system. The only issue that has occurred is client disconnectivity on cluster failover but, the Administrator knows all that is required is to go into the systeminfo table and reset the ping field to SVS1 and all is well again. |
|
|
|
Re: SLX 6.2 and Clustered SQL Servers
Posted: 19 Apr 06 8:23 AM
|
fiogf49gjkf0d Thanks everyone for your responses! I greatly appreciate them.
The threads here all indicate it will work fine as long as you have an application server that houses the OLE-DB provider on a box that is not part of the cluster. Frankly, doesn't this defeat the whole point of clustering in that there is now a single point of failure?
Another question - do I point the ping server to the "virtual" SQL server (the cluster), or point it to the active server that is part of the cluster? |
|
|
|
Re: SLX 6.2 and Clustered SQL Servers
Posted: 19 Apr 06 8:33 AM
|
fiogf49gjkf0d You would point the ping server to the Virtual server not the actual server. The actual server address will give you a message regarding this not being an active connection or something to that effect. |
|
|
|