Re: SqlExpress Merge Agent slow Profiles & one way Rep

I have to ask. Are you certain that that is how it works? Can you point me at
something in Books Online that says Pull Subscribers get profiles from the
Publisher.

I have a publishing subscriber which publishes to SQLExpress.

You are saying that if I set "slow profile" on the publisher SQLExpress will
use that?

I also have merge agents pulling data from the master to the publishing
subscriber machine. Are you saying these will "ignore" my "slow" setting and
get their profile from the master publisher?

You have said I can override these on the client by creating a profile on
the publisher and saying with subscriber should use it. How do I do that?

Also if the values are sent from the server, why does SQL2008 have
properties on the "client" to set these values without using profiles.

Thanks for taking the time to answer...

Cliff

"Hilary Cotter" wrote:

It works because the pull agent gets the profile information from the
publisher, just like it gets ftp info.

Note you can override these values on the client and if you create a profile
based off one of the default profiles and select which subscriber should use
it.
"Gatecrasher" <Gatecrasher@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:776BC783-220E-447B-A7C6-E931801AAD35@xxxxxxxxxxxxxxxx
Sorry that makes no sense to me!

if the profiles are kept on the publisher why does my code not work? You
are
saying the msdb table is missing on SQL Express (the subscriber) but if
the
profile used by express is on the publisher it shouldn't matter??

Surely the profiles exist where the Agent runs, which for a Merge agent is
the subscriber. Surely they exist on every installation (except express it
seems)

Are you saying that my Agent on the subscriber gets it's profile from the
publisher and overlays the values.

When you "set default - slow profile" for ALL Merge Agents on a server are
you setting them for the Merge Agents that run on that server or for the
merge agents that subscribe to that server. I assumed the former.

I think this is flaw in SQL Express 2005. It is fixed in 2008.

2005 Express has been cut down and that table in msdb removed. the side
effect is that you cannot create and use profiles against agents. There
is
no physical way to "create" a profile because that table is missing. You
are
stuck with using the default values. Changing the default profile on the
distributer will only change the settings for the Merge Agent on that
instance surely.

In 2008 they have exposed these properties on the agent without the need
to
create a profile. I assume they are exposing the default profile which you
can tweak through these properties.



"Hilary Cotter" wrote:

The profiles are kept on the publisher. The slow agent profile is ideal
for
low bandwitdth links between your publisher and tthe subscriber.

SQL Express does not have an msdb database which your code is looking for
on
the subscriber. This is why it won't work.

"Gatecrasher" <Gatecrasher@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1EF0C287-68F3-4213-B32A-834150566D65@xxxxxxxxxxxxxxxx
I want to make this SQLExpress clients Agent use the "Slow connection"
profile. Setting slow profile on the server I assume does nothing for
me
at
all??? I assume that because the Agent runs on the client. Correct?

So does a SQLExpress install have "agent profiles" given it doesn't
have a
real Agent at all?

i thought I would try something obvious

AgentProfile profile = new AgentProfile();
profile.Name = "My Profile";
profile.AgentType = AgentType.MergeAgents;
profile.ConnectionContext = conn;
profile.Create();
MergeSynchronizationAgent agent = subscription.SynchronizationAgent;
profile.AddParameter("-DownloadGenerationsPerBatch", "1");
agent.ProfileName = "My Profile";

but this fails because the profile.Create() dies with

_innerException = {"Invalid object name 'msdb..MSagent_profiles'."}

Required table missing

Am i just missing the point here that SQLExpress does not allow you to
set
values on the Agent?? If that is the case how can I change my batch
size
for
slow connections?

If I google this

MergeSynchronizationAgent.DownloadGenerationsPerBatch

I get a new property for SQL 2008 but it only shows up for MSDN in the
German site!!

I installed SqlExpress 2008 and after a bit of messing around, the
SqlServer.Replication.DLL is not in the GAC when it used to be, this
new
Property exists.

I wonder if it will find its way back into 2005, without it I am
stumped.
Also discovered cannot Merge Replicate from 2005 Publisher to 2008
Subscriber, not allowed.

Any ideas?




.

Relevant Pages

  • Re: Network traffic with transactional replication with immediate updates (SQL 2005)
    ... I do not need to wait until off-hours to run a trace on the subscriber. ... Specifies whether the agent attempts to poll replicated transactions ... profile for distributor agents has as profile parameters one called ... I cannot find a way to explain why Distributor Agents are to ...
    (microsoft.public.sqlserver.replication)
  • Re: SqlExpress Merge Agent slow Profiles & one way Rep
    ... The slow agent profile is ideal for low bandwitdth links between your publisher and tthe subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: undocumented agent profile parameters
    ... dedicated when you the merge replication related procs and commands are run ... I would venture to say that the performance of the merge agent is more ... When I hear the words performance and blocking on the publisher with ... Is "source" a publisher or subscriber? ...
    (microsoft.public.sqlserver.replication)
  • RE: Merger Replication - SQL2000
    ... you cannot use SQL2000 subscriber to merge when publisher is SQL2005. ... snapshot, and use nosync option when creating subscription, the merge agent ... we were unable to get merger replication to work ...
    (microsoft.public.sqlserver.replication)
  • Re: changing merge agent profile for HTTPS - mergeSubscriberType = anonymous
    ... Looking for a SQL Server replication book? ... Just to confirm, for dim old me, if I want to change the profile for one ... subscriber, I need to change it at the subscriber in my RMO code - ... get the agent at the publisher/distributer use a slower profile - I've ...
    (microsoft.public.sqlserver.replication)
Loading