Re: Optimisation

Tech-Archive recommends: Fix windows errors by optimizing your registry



With a remote publisher/distributor its on the distributor, with a local
publisher/distributor its on the publisher.

Basically you do it wherever your distribution agents run.

Its normal for the OutputVerboseLevel parameter not to be used.
--
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

"GC" <GC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9B8F89FB-1106-48F2-9ED6-AC2BC752333B@xxxxxxxxxxxxxxxx
> Hi,
>
> I read that we can optimise from 10 to 15 % the performance of a
> replication
> by changing the default value of the HistoryVerboseLevel and the
> OutputVerboseLevel of the Agent Profiles
>
> For exemple for the Distribution Agent we have to use
> distrib -HistoryVerboseLevel 1
> distrib -OutputVerboseLevel 0
>
> The default value are 2 for both
>
> The distrib program to executable is in
> C:\Program Files\Microsoft SQL Server\80\COM
>
> 2 questions
>
> 01- On which server I have to execute this command on the Distributor or
> on the
> Publisher
>
> 02- Also when i go on the Distributor and view the propreties of the
> Agent
> profile
> I dont see the OutputVerboseLevel. Is that normal
>
> Thanks in advance !
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


.



Relevant Pages

  • Re: create an msde replica in access db?
    ... Execute sp_adddistributor at the server that will be the Distributor. ... Execute sp_adddistpublisher at each server that will be a Publisher ... distribution database, working directory, and SQL Server Agent user ...
    (microsoft.public.access.adp.sqlserver)
  • Object name MSsubscription_agents invalid
    ... Using SQL Server Enterprise in the Publisher/Distributor and Sql Server 2000 ... in the distributor. ...
    (microsoft.public.sqlserver.replication)
  • Distributor
    ... How do you clear out the distributor? ... how do I clear out the distributor assuming that it's trying to ... execute a sproc that might not have been replicated? ...
    (microsoft.public.sqlserver.replication)