>-----Original Message-----
>Hi,
>
>We have a replicated database which has quite a complex
DB model with a lot
>of related tables (the DB is for a content management
system). When a user
>performs a delete operation on the publisher and it is
run on the subscriber
>it use 100% CPU and really slows down the machine
(because of the number of
>deletes I guess).
>
>Is there a way to run the the replication process at
below normal priority
>so it does not tie up the server?
>
>What happens if you run the SQL server process at below
normal priority? Or
>is there a way to throatle SQL Server CPU usage?
>
>Also is there a way to execute individual SPs at below
normal priority?
>
>Most grateful for any info
>Pete
>
>
>.