... help me ... urgent..
Wouldn't it be a wise idea to first test a little bit with the technology ?
- So you know how to:
* put in place
* monitor
* follow up
* troubleshoot
* handle failover
....
- So you can determine the usage mode based on sound knowledge and your companies need.
- Keep in mind your applications connections will need to be modified. They will have to use SQLNCLI !
Also keep in mind DBMirroring is not supported in all cases !!
http://technet.microsoft.com/en-us/library/ms366279.aspx
Database mirroring is not supported with either cross-database transactions or distributed transactions. This is because transaction atomicity/integrity cannot be guaranteed for the following reasons:
For cross-database transactions: After a failover, the mirrored database is on a different server instance, and typically it is on a separate database from the nonmirrored database. Even if both databases are mirrored between the same two partners, there is no guarantee that both databases will fail over at the same time.
For distributed transactions: After a failover, the new principal server is unable to connect to the distributed transaction coordinator of the previous principal server that uses the same resource ID. Therefore, the new principal server cannot obtain the transaction status.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me