February 16, 2009 at 5:42 am
Hi,
I recommend you to check out BOL so that you can get more info there.
Thanks
Chandra Mohan N
[font="Verdana"]Thanks
Chandra Mohan[/font]
February 16, 2009 at 6:12 am
I have read through BOL for data mirroring and setup a test environment for database mirroring, however there are a number of things I am unclear on, hence my post her........
February 16, 2009 at 9:42 am
For your question #1, taken from BOL:
To force service in a database mirroring session
1. Connect to the mirror server.
2. Issue the following statement:
ALTER DATABASE SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS
where is the mirrored database.
The mirror server immediately transitions to principal server, and mirroring is suspended.
As the option states, any transactions that have not been updated from the (former) Principal are lost when you execute this command.
February 16, 2009 at 9:55 am
Question #2, also taken from BOL:
Database mirroring partners and witnesses are supported by SQL Server 2005 Standard SP1 and later versions, and by SQL Server 2005 Enterprise Edition SP1 and later versions. But the partners must use the same edition, and asynchronous database mirroring (high-performance mode) is supported only by SQL Server 2005 Enterprise Edition SP1 and later versions. Witnesses are also supported by SQL Server 2005 Workgroup SP1 and later versions and by SQL Server 2005 Express Edition SP1 and later versions.
February 16, 2009 at 9:57 am
And, on question #3, depending on your setup, changes on the Principal are usually reflected almost instantly on the mirror, not within minutes, so yes, any data deleted from Principal, must be restored on Principal....
Viewing 5 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply