Hi, This certainly depends upon the business logic and organizational need, allowed latency time and whether automatic fail over is required or not; based on this you can select any out of this four option 1.) Automatic Fail-Over -->a) Cluster -->b) Mirroring 2.) Manual Fail-Over -->a) Replication...

Hi, yes this will do and apply the changes.

Hi, Yes, we can very much change the physical file name as well, ALTER DATABASE testdb MODIFY FILE ( NAME = test, filename='somepath\newphysical_filename.mdf' ); go

Hi, Configuring and setting up High Availability depends upon the need of your environment and organizational/business process, what and how they would like to achieve high availability with SQL Server, and based on this analysis you can have 1. Clustering 2. Replication 3. Log Shipping 4. Database Mirroring...

Hi, DB Mirroring will give you automatic fail-over, and this is the advantage over Log Shipping. Refer http://technet.microsoft.com/en-us/magazine/cc160992.aspx

Hi, As Satya have suggested Clustering & DB Mirroring would be the best choice, but it depends up to what level and what kind of solution your environment demands and based on that you could choose one/many/all of Clustering, Replication, Mirroring and Log Shipping. And its high time to update your...