Thanks for this response Hilary.
point us to a log reader issue, which I will investigate further. One
i.e. sp_who2 to find out what processes are running. Are there any
On 29 Jan, 16:08, "Hilary Cotter" <hilary.cot...@gmail.com> wrote:
> I've seen this. First off 100% cpu utilization means your processor is very
> busy which is not a bad thing per se. Use task manager to discover what
> component on your server is consuming the most amount of CPU. If it is the
> log reader you may be bumping into a problem where the article cache gets
> locked. Please refer to
http://support.microsoft.com/kb/812263/en-us >
> I still see something like this on SQL 2005, especially when on my laptop
> when I go back and forth between hibernations and suspensions. I take it
> your production environment is not running on laptops right;)?
>
> One option is to kill the log reader agent and then to restart it.
>
> --
> Hilary Cotter
>
> Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html >
> Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com >
> <batballs2...@hotmail.com> wrote in messagenews:1170074757.988440.201880@s48g2000cws.googlegroups.com...
>
> > We have recently installed a new SQL Server 2005 box to compliment our
> > existing SQL Server 2000. To ensure data consisitentcy we have
> > employed replication between the two servers. We are using
> > transactional replication, with the replication being applied at
> > scheduled times during the day. The problem seems to be a short while
> > after the replication has completed (up to 30 mins) the publisher /
> > distributor server (SQL Server 2005) cpu maxes out at 100%. This can
> > only be recovered by a server re-boot.
>
> > Can anyone shed any light / thoughts on this area.
>
> > Many thanks in advance
>
> > Mark
