Dear all, I'm concerned with the following issue: After the setup of Log shipping on high -intensive system, running on SQL Server 2005 Enterprise EDition SP4, there is 100 % CPU usage SQL Server average CPU - above 90 on the primary server and also high intensive I/O caused by SQL Server. In this relation I wanted to ask you whether you have experienced some problems with the performance of the primary server after the Logshipping setup - as I/O high and CPU high and where exactly could be the cause? Log shippping so far as I read would have a little or no impact on the application performance on the primary server. There is no large Transaction log and also after disabling of Log shipping at 11:00 a.m the problem remains till 18:00 p.m ( in the intensive work hours with the system). All session are from the IIS. Thanks in advance. I would be very thankful If somebody could explained exactly how Log shiiping impacts the performance of the primary server and which is the cause nad eventually the solution.
Although log shipping add some overhead of taking log backups after specific interval but in most transaction processing environments, taking transaction log backups is necessary and normal, so I do not think that it would be the problem. But Log shipping does add some disk and network overhead since it has to copy the backup files to the standby server periodically. If you have a large number of transactions you should check your network and disk performance. I believe this will lead you to the root cause.
I configured before 2 weeks Log shipping without Monitor server again, and now is running. The performance on the primary server is ok after the second setup. Thanks to all for the replies and the motivation to setup Log shipping again. ( The performance issue was caused by extensive I/O workload by Application Windows service.