What are the best practices for suspending a non-clustered/non-fault tolerant SQL 2008 server for maintenance?
We have a SQL 2008 server in a hosted environment. The transaction log files and the DB files sit on SAN LUNS presented to the physical SQL server. Our host/vendor is migrating all data off that current SAN to a new SAN. Therefore, I want to stop all SQL prior to the move, then bring SQL back online after the SAN migration is complete.