Log Shipping VS Database Mirroring

转载于 2011-10-09 15:06:32 发布 · 703 阅读

文章标签：

#database #transactions #.net #tcp #up

Sql Server 专栏收录该内容

33 篇文章

订阅专栏

本文对比了使用Log Shipping和Database Mirroring进行数据库复制的技术，包括数据传输、事务一致性、服务器限制、故障转移、角色变化和客户端重定向等方面。Log Shipping允许将事务日志备份并转移到多个备用服务器上，而Database Mirroring则通过TCP端点仅传输已提交的事务记录，并且可以自动进行故障转移。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

With Log Shipping:

Data Transfer:    T-Logs are backed up and transferred to secondary server
Transactional Consistency: All committed and un-committed are transferred
Server Limitation:   Can be applied to multiple stand-by servers
Failover:   Manual
Failover Duration:  Can take more than 30 mins
Role Change:   Role change is manual
Client Re-direction:  Manual changes required

With Database Mirroring:

Data Transfer:    Individual T-Log records are transferred using TCP endpoints
Transactional Consistency: Only committed transactions are transferred
Server Limitation:   Can be applied to only one mirror server
Failover:   Automatic
Failover Duration:  Failover is fast, sometimes < 3 seconds but not more than 10 seconds
Role Change:   Role change is fully automatic
Client Re-direction:  Fully automatic as it uses .NET 2.0