February 7, 2006 at 2:56 pm
We are building a disaster recovery environment for SQL Server-based production application with a mirror site. We plan to synchronize data at disk or LUM level between primary site and mirror site. Is there a way to change the Production server into a read-only mode (or hot backup mode in Oracle term) while synchronizing the data and change it back when synchronization is done?
Any help is greatly appreciated.
Thanks!
February 7, 2006 at 3:35 pm
A number of database state options are available, including (refer BOL under 'ALTER DATABASE'):
< state_option > ::=
{ SINGLE_USER | RESTRICTED_USER | MULTI_USER }
| { OFFLINE | ONLINE }
| { READ_ONLY | READ_WRITE }
In your case, try:
ALTER DATABASE [database name] SET READ_ONLY
February 7, 2006 at 6:05 pm
Thanks for the response. That helps.
But, I really want to find out if I could make entire SQL server in read-only mode with a simple command since I have multiple databases on that server. Also, if a database is being used, it can not be changed to read-only mode.
February 8, 2006 at 3:09 am
Hi Leezhang
Check BOL for Log Shipping and/or Replication which both automate server synchronisation.
February 8, 2006 at 11:32 am
If you are using LUN replication, why not just leave the SQL Server Service off at the DR site until needed ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
February 8, 2006 at 11:39 am
Yes, we are using LUM replication. I am not concerned with the SQL server on DR site. I am concerned with SQL server on primary production site. Is there a mode in SQL like Oracle's hot backup mode?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply