greetings - we have SQL Server 2008 R2, and am in the process of setting up mirrored databases with a witness server. We wanted complete transparency, so we were hoping to use Windows Clustering to provide a virtual IP address so that users wouldn't need to modify their connection strings at all. Alas, for whatever reason, Windows Clustering isn't going to work, so I'm faced with a dilemma.
1) the .net apps can change their connection strings to recognize a principal and a mirror - that is fine, but what about our dozens of SSIS jobs and other ETL (Talend, Pentaho etc) jobs? Is there a way for these jobs to use a principal/mirror setup and/or a virtual IP address?
2) I could go with MSCS but then I have the single point of failure with the DB, and my experience in the past using DoubleTake/Geocluster to do a stretch cluster was slightly sketchy.
any opinions or solutions?