SQL Server 2005事务复制性能
[英]SQL Server 2005 transactional replication performance
问题描述
Does anybody know how transactional replication have impact to performance of publisher database? 
有人知道事务复制如何影响发布者数据库的性能吗？ I want to use a subscriber as a base for generate on-line reports and statistics (use transactional replication for copy data), but I don't know how it could reduce performance of source database (or not). 我想使用订阅服务器作为生成在线报告和统计信息的基础（使用事务复制复制数据），但是我不知道它如何降低（或不降低）源数据库的性能。
The source server: SQL 2005 Standard, VMWare, 4 CPU (16 cores), 16 GB RAM 源服务器：SQL 2005 Standard，VMWare，4个CPU（16个内核），16 GB RAM
The destination server: SQL 2005 Standard, VMWare, 1 CPU (4 cores), 8 GB RAM 目标服务器：SQL 2005 Standard，VMWare，1个CPU（4核），8 GB RAM
1 个解决方案
解决方案1
1 2012-05-11 02:51:29
Well... yes and no. 好吧，是，不是。 Transactional replication is asynchronous, so it's not as though your performance will slow down merely because there's a publication. 事务复制是异步的，因此这似乎并不是因为发布而导致性能下降。 However, depending on how much extra horsepower you have to spare on the server right now, the log reader might put you over the top. 但是，根据您现在必须在服务器上保留多少额外的功能，日志阅读器可能会让您处于顶峰。 Also note that the semantics of when a log record can be cleared from the transaction log change with transactional replication, so be careful there. 还要注意，可以通过事务复制从事务日志中清除日志记录的语义会随着事务复制而改变，因此请务必注意。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.