LogShipping Restore Read Only to Read-Write | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

LogShipping Restore Read Only to Read-Write

Can you help me telling how to change my read-only secondary server (marked as ‘standby#%92 in my log-shipping plan and where the logs are shipped) as a read-write DB after the log-shipping is done? The alter db statement is failing to make it read-write. We have Test, Staging and Production environments. Once in every week (Sundays), the staging-environment is refreshed with production data for testing purpose. This is done manually by backup-production-and-copy-to-another-server-and-restore etc. which is tedious and time taking. My plan is to accomplish this by log-shipping once a week i.e. at a load delay of 192 hours. But I am at a loss on how to allow the users to use it after the log-shipping is done (read-only to read-write) and do the log-shipping automatically at the end of the week? Can you please help? Best Regards
What is the reason behind enabling the STANDBY database to read-write which will fail the Log shipping process as a whole? You can deploy your own log shipping process in this case instead of using SQL supplied LS wizard with maint. plans. Can take help from thishttp://www.sql-server-performance.com/sql_server_log_shipping.asp&e=7415 link about performing own Log shipping. HTH Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.