I'd raise that as s support call with your local provider as I don't think LDSD supports that type of setup. Normally you'd connect to a single cluster and let the SQL cluster take care of any switching between particular servers.
I had a similar situation when I upgraded to 7.5 - we have a mirrrored database with automatic failover, the only apparent difference to you being that we use integrated authentication. I also found, like you, that when I set it up (by checking the "Specify as connection string" box) it would then revert back and lose the failover partner settings.
Now, I can't be 100% sure (it was a little while ago), but I think that if I set up the connection string and then didn't go back into it afterwards to edit, I think that worked for me.
LANDesk is functioning successfully for me regardless of which database server is the principal.
P.S. - I know I had problems initially on v7.4 when I set it up mirroring with failover with SQL authentication, as the SQL account that I was connecting with existed on one server, which wasn't the same account on the mirrored server.
I thought that Landesk is supporting any kind of HA database as long it is MS SQL or Oracle
In manual is example of big enviroment where DB is mirrored on two MS failover clusters, so mine is even simpler
Paul - I'll try your solution, maybe will work on 7.5.
I'd recommend you discuss this with your support team, just to make sure the best practise approach is being used.
I've tested system, and summary is:
- I can enter connection string directly to config file http://community.landesk.com/support/docs/DOC-3685 (Thanks support for that link)
- as long as "ok" button is not clicked in control centre - string remains unchanged, and value entered first time with connection string checkbox checked is still there - as suggested by Paul
- ServiceDesk on mirrored database with SQL authentication works ok, but you have to create login on mirror server with same SID as is on principal.
- LANDesk support is checking why connection string disappears from configuration center window.