SQL High Availabilty
-
All, Just looking for peoples advice based on experience with sql high availability. Basically in the past we have used SQL Clustering without any issues for high availability, I have used this in many companies how ever we are currently moving environements which I will not have the option to use clustering. So basic setup, two sql servers (active/passive roles) running SQL 2008 standard, database files are stored on a high speed SAN. So need some options, I know I can use log shipping, however failure time is >1min. Also for patching how do I restart a server and ensure the other server which is being logged shipped to has the latest data ? Mirroring is a option, however according to MS mirroring should not be used on more than 10 databases. We have lots more! The last option which seems bad practice but could work is simply kill all users, detach db's and then reattach to other server. Any issues with this ? Ignore any issue with client connectivity based on server names, this can be resolved in different ways. Any real advice appreciated, I have read most of the SQL documentation so no need to just forward me to there :) Thanks Shane