Replication error....

We try to perform replication. We configured our server for
replication. Steps that we followed:
1) Create Publishing and distribution wizard
2) Create Publication wizard
3) Create Pull subscription wizard
We did not meet any errors until while doing them. But at the end of
the process in the replication monitor red cross signs (As seen in
http://stx.cs.deu.edu.tr/~zbektas/er.JPG ) on the publishers and
subscribers and their status seem as "failed". Why?
We can not start the SQL agent because of "the service did not start
due to a logon failure" error. Is this error related with our
replication failure?
Zafer,
SQL Server Replication infrastructure involves many things including a series of jobs which are scheduled and run by the SQL Server Agent. So, if your agent is stopped, replication won't work. Try changing the SQL Server Agent service to use the same doma
in account as your SQL Server Service and then restart it, and then run the Replication Agents.
Regards,
Paul Ibison
|||This is likely your problem. Locate your SQL Server agent and ensure it is
running with a valid account and password.
"zafer" <zaferbektas2000@.yahoo.com> wrote in message
news:c71dc7b.0404020741.2519351e@.posting.google.co m...
> We try to perform replication. We configured our server for
> replication. Steps that we followed:
> 1) Create Publishing and distribution wizard
> 2) Create Publication wizard
> 3) Create Pull subscription wizard
> We did not meet any errors until while doing them. But at the end of
> the process in the replication monitor red cross signs (As seen in
> http://stx.cs.deu.edu.tr/~zbektas/er.JPG ) on the publishers and
> subscribers and their status seem as "failed". Why?
> We can not start the SQL agent because of "the service did not start
> due to a logon failure" error. Is this error related with our
> replication failure?

Replication Error of MS SQL server2k

Distribution Agents come with a error and stop between two SQL2000 server.
The error messages is:

The query processor could not produce a query plan from the optimizer
because a query cannot update a text, ntext, or image column and a
clustering key at the same time. (Source: Some Server (Data source); Error number:
8629)

How can I fix it?Is it transactional replication?
If yes - and you are using Identity fields (with not for replication) then check prsp_MSupd_**** stored procedures on subscriber and remove updating Identity field.

replication distribution server agents keep time out

Hi,
We have a distribution server that have all of our
transactional replications on it. All the distribution
agents and log reader agents keep time out and we have to
keep restart the agents.
What's the roob cause of this? Too many replications on
one distribution box? Or too many agents running at the
same time schedule?
Many thanks.
JJDon't the distribution agents keep trying for a certain number of times
before they error out? While they keep trying, you don't need to manually
restart them.
Distribution agents often times out in our environment. Causes I have found
are:
1. Blocking on the subscriber;
2. No more space on the subscriber database;
3. Server connection problem;
Richard
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:01a501c39284$479d5ee0$a401280a@.phx.gbl...
> Hi,
> We have a distribution server that have all of our
> transactional replications on it. All the distribution
> agents and log reader agents keep time out and we have to
> keep restart the agents.
> What's the roob cause of this? Too many replications on
> one distribution box? Or too many agents running at the
> same time schedule?
> Many thanks.
> JJ

Replication distribution cleanup error

I used the SQL Server 2005 publication wizard to set up transactional replication. It scheduled a job called "Distribution clean up: distribution" that calls sp_MSdistribution_cleanup. The job fails every time it runs. The xp_cmdshell is enabled and SQL Server Agent runs under an account that has sufficient privileges to execute it. The account also has full rights to the repldata subdirectories. I have applied service pack 1.

I looked through the sp_MSdistribution_cleanup code and it looks like there are two stored procedures and one function missing from the SQL server databases. They are

master.dbo.sp_MSunc_to_drive sys.fn_escapecmdshellsymbolsremovequotes sys.sp_MSdrop_distribution_agentid

Where can I get a copy of these stored procedures? The expired distribution data is slowly consuming my remaining hard drive space. Thanks.

Joe

Hi, Joe,

There seems to be a bug in our code where we should not call master.dbo.sp_MSunc_to_drive, instead we should call sys.sp_MSunc_to_drive. In SQL Server 2005, we have move most of the system sps to mssqlsystemresource database, and some of them are hidden from end users as they're not supposed to be used directly by customers. sys.sp_MSunc_to_drive, sys.fn_escapecmdshellsymbolsremovequotes and sys.sp_MSdrop_distribution_agentid are hidden sps/function thus you don't see them but they do exist.

I will do more research and see if there is a workaround.

By the way, can you post the exact error message you're seeing from distribution cleanup job (by using replication monitor to view the job history)? Are you using dynamic snapshot merge replication? Any specific information about your replication setup would be helpful.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks for answering me so quickly. The problem has been resolved. The account under which xp_cmdshell was executing did not have the proper access to the repldata share.

Joe

|||

Glad to hear that the problem is solved. The issue mentioned in my post is a minor issue and should not cause any functional problems. It would be helpful for other visitors of this thread if you can post the error message you're seeing before it's fixed (it should still be available in replication agent history).

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I'm really sorry, but the clean up agent already deleted the history. I think part of the message was "Could not clean up the distribution transaction tables."

Joe

sql

Replication Distribution Agent Does Not Start

Hi,
For some magical reason, my database replication has suddenly stopped
working. I modified the publication but the Distribution agent will
not run; the snapshot does not get applied to the subscriber, and
changes made at the publisher do not get replicated.
My configuration is: Transactional Replication with a
‘Pull’ Subscription. The Subscriber is Updateable with
Immediate Updates Only. All created via the SQL Server Enterprise
Manager. Both the Publisher and Subscriber are on the same server.
I’m running SQL Server 2000 (8.00.760 SP3), on Windows 2000
Server (5.0 (2195)).
I manually run the snapshop agent. It runs fine with the status
‘Succeeded’ and the Last Action is ‘A Snapshot of X
article(s) was generated’.
When I look at the distribution agent, things start to get a bit
confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
<SERVERNAME?>/ Publication/ Subscription), the status stays
constantly at ‘Never Started’. All other columns are
either blank or 0. When I right click over the subscription, both
Start Synchronising and Stop Synchronising are NOT greyed out. If I
click on either Start Synchronising or Stop Synchronising (absolutely)
nothing happens (except the mouse turns ‘busy’ for a
fraction of a second). There are no error messages.
I added -output c:\sqlout.txt -outputverboselevel 3 to the
distribution agent command. C:\sqlout.txt did not get created.
It worked fine up to a couple of days ago. I’m not sure exactly
what caused the problem, as I made a few changes at the same time. The
changes included: adding a new transactional publication, adding more
articles to an existing transaction publication, and adding a merge
publication. I’ve tried to go back to the set up before I made
the changes, even disabling replication and starting again from
scratch. Still the problem persists.
The owner of the distribution agent has dbo permissions in both the
publishing and subscribing database. Under ‘Publisher and
Distributor Properties’ I’ve set the ‘Replication
Agent Connection to Publisher’ and ‘Agent Connection to
the Subscriber’ both to Use SQL Server Authentication, both with
the same account that has dbo permissions in both publishing and
subscribing database.
Has anybody come across anything like this before? Can anybody make
any suggestions? Thanks in advance for your help.
Regards
Damian Helme
IS Manager
INTEC Engineering (UK) Ltd.
are you using an ActiveX control or Windows Synchronization Manager to
manage this subscription? If so you will not be able to manage your
distribution agent in EM.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Damian H" <damianhelme@.hotmail.com> wrote in message
news:2b893e38.0407220153.32af854e@.posting.google.c om...
> Hi,
> For some magical reason, my database replication has suddenly stopped
> working. I modified the publication but the Distribution agent will
> not run; the snapshot does not get applied to the subscriber, and
> changes made at the publisher do not get replicated.
> My configuration is: Transactional Replication with a
> ‘Pull’ Subscription. The Subscriber is Updateable with
> Immediate Updates Only. All created via the SQL Server Enterprise
> Manager. Both the Publisher and Subscriber are on the same server.
> I’m running SQL Server 2000 (8.00.760 SP3), on Windows 2000
> Server (5.0 (2195)).
> I manually run the snapshop agent. It runs fine with the status
> ‘Succeeded’ and the Last Action is ‘A Snapshot of X
> article(s) was generated’.
> When I look at the distribution agent, things start to get a bit
> confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
> <SERVERNAME?>/ Publication/ Subscription), the status stays
> constantly at ‘Never Started’. All other columns are
> either blank or 0. When I right click over the subscription, both
> Start Synchronising and Stop Synchronising are NOT greyed out. If I
> click on either Start Synchronising or Stop Synchronising (absolutely)
> nothing happens (except the mouse turns ‘busy’ for a
> fraction of a second). There are no error messages.
> I added -output c:\sqlout.txt -outputverboselevel 3 to the
> distribution agent command. C:\sqlout.txt did not get created.
> It worked fine up to a couple of days ago. I’m not sure exactly
> what caused the problem, as I made a few changes at the same time. The
> changes included: adding a new transactional publication, adding more
> articles to an existing transaction publication, and adding a merge
> publication. I’ve tried to go back to the set up before I made
> the changes, even disabling replication and starting again from
> scratch. Still the problem persists.
> The owner of the distribution agent has dbo permissions in both the
> publishing and subscribing database. Under ‘Publisher and
> Distributor Properties’ I’ve set the ‘Replication
> Agent Connection to Publisher’ and ‘Agent Connection to
> the Subscriber’ both to Use SQL Server Authentication, both with
> the same account that has dbo permissions in both publishing and
> subscribing database.
> Has anybody come across anything like this before? Can anybody make
> any suggestions? Thanks in advance for your help.
> Regards
> Damian Helme
> IS Manager
> INTEC Engineering (UK) Ltd.
|||Hillary
Thanks for your reply. No I am not using an ActiveX control or Windows
Synchronization Manager. It is all done through EM.
Here's the post again, but this time free of the garbled control
characters:
================================================== =============================
Hi,
For some magical reason, my database replication has suddenly stopped
working. I modified the publication but the Distribution agent will
not run; the snapshot does not get applied to the subscriber, and
changes made at the publisher do not get replicated.
My configuration is: Transactional Replication with a 'Pull'
Subscription. The Subscriber is Updateable with Immediate Updates
Only. All created via the SQL Server Enterprise Manager. Both the
Publisher and Subscriber are on the same server. I'm running SQL
Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).
I manually run the snapshop agent. It runs fine with the status
'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
generated'.
When I look at the distribution agent, things start to get a bit
confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
<SERVERNAME?>/ Publication/ Subscription), the status stays
constantly at 'Never Started'. All other columns are either blank or
0. When I right click over the subscription, both Start Synchronising
and Stop Synchronising are NOT greyed out. If I click on either Start
Synchronising or Stop Synchronising (absolutely) nothing happens
(except the mouse turns 'busy' for a fraction of a second). There are
no error messages.
I added -output c:\sqlout.txt -outputverboselevel 3 to the
distribution agent command. C:\sqlout.txt did not get created.
It worked fine up to a couple of days ago. I'm not sure exactly what
caused the problem, as I made a few changes at the same time. The
changes included: adding a new transactional publication, adding more
articles to an existing transaction publication, and adding a merge
publication. I've tried to go back to the set up before I made the
changes, even disabling replication and starting again from scratch.
Still the problem persists.
The owner of the distribution agent has dbo permissions in both the
publishing and subscribing database. Under 'Publisher and Distributor
Properties' I've set the 'Replication Agent Connection to Publisher'
and 'Agent Connection to the Subscriber' both to Use SQL Server
Authentication, both with the same account that has dbo permissions in
both publishing and subscribing database.
Has anybody come across this problem before? Can anybody make any
suggestions? Thanks in advance for your help.
Regards
Damian Helme
IS Manager
INTEC Engineering (UK) Ltd.
|||I've encountered this error before and its driving me crazy trying to recall
exactly what is causing it. IIRC its something pretty simple.
Can you right click on your distribution agent, select agent properties
select steps, click on Run Agent, and click edit.
Then copy everything in the commands text box.
Open a command window and go to c:\program files\microsoft sql server\80\com
and then type
distrib and paste your commands here. To do this, go to the c:\ thingy in
the upper left hand corner of your command window and select edit - paste.
Make sure there is a space between distrib and the commands.
Then hit enter. You should get an error message this time.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Damian H" <damianhelme@.hotmail.com> wrote in message
news:2b893e38.0407222334.bc69d37@.posting.google.co m...
> Hillary
> Thanks for your reply. No I am not using an ActiveX control or Windows
> Synchronization Manager. It is all done through EM.
> Here's the post again, but this time free of the garbled control
> characters:
>
>
================================================== ==========================
===
> Hi,
> For some magical reason, my database replication has suddenly stopped
> working. I modified the publication but the Distribution agent will
> not run; the snapshot does not get applied to the subscriber, and
> changes made at the publisher do not get replicated.
>
> My configuration is: Transactional Replication with a 'Pull'
> Subscription. The Subscriber is Updateable with Immediate Updates
> Only. All created via the SQL Server Enterprise Manager. Both the
> Publisher and Subscriber are on the same server. I'm running SQL
> Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).
> I manually run the snapshop agent. It runs fine with the status
> 'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
> generated'.
> When I look at the distribution agent, things start to get a bit
> confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
> <SERVERNAME?>/ Publication/ Subscription), the status stays
> constantly at 'Never Started'. All other columns are either blank or
> 0. When I right click over the subscription, both Start Synchronising
> and Stop Synchronising are NOT greyed out. If I click on either Start
> Synchronising or Stop Synchronising (absolutely) nothing happens
> (except the mouse turns 'busy' for a fraction of a second). There are
> no error messages.
> I added -output c:\sqlout.txt -outputverboselevel 3 to the
> distribution agent command. C:\sqlout.txt did not get created.
> It worked fine up to a couple of days ago. I'm not sure exactly what
> caused the problem, as I made a few changes at the same time. The
> changes included: adding a new transactional publication, adding more
> articles to an existing transaction publication, and adding a merge
> publication. I've tried to go back to the set up before I made the
> changes, even disabling replication and starting again from scratch.
> Still the problem persists.
> The owner of the distribution agent has dbo permissions in both the
> publishing and subscribing database. Under 'Publisher and Distributor
> Properties' I've set the 'Replication Agent Connection to Publisher'
> and 'Agent Connection to the Subscriber' both to Use SQL Server
> Authentication, both with the same account that has dbo permissions in
> both publishing and subscribing database.
> Has anybody come across this problem before? Can anybody make any
> suggestions? Thanks in advance for your help.
> Regards
> Damian Helme
> IS Manager
> INTEC Engineering (UK) Ltd.
|||Thanks for the suggestion, I didn't get chance to try your suggestion
as I had already reinstalled SQL Server, which solved the problem.
I'll keep a note of your suggestion for future use.
Thanks again.
Damian.

Replication Distribution Agent Does Not Start

Hi,

For some magical reason, my database replication has suddenly stopped
working. I modified the publication but the Distribution agent will
not run; the snapshot does not get applied to the subscriber, and
changes made at the publisher do not get replicated.

My configuration is: Transactional Replication with a 'Pull'
Subscription. The Subscriber is Updateable with Immediate Updates
Only. All created via the SQL Server Enterprise Manager. Both the
Publisher and Subscriber are on the same server. I'm running SQL
Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).

I manually run the snapshop agent. It runs fine with the status
'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
generated'.

When I look at the distribution agent, things start to get a bit
confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
<SERVERNAME?>/ Publication/ Subscription), the status stays
constantly at 'Never Started'. All other columns are either blank or
0. When I right click over the subscription, both Start Synchronising
and Stop Synchronising are NOT greyed out. If I click on either Start
Synchronising or Stop Synchronising (absolutely) nothing happens
(except the mouse turns 'busy' for a fraction of a second). There are
no error messages.

I added -output c:\sqlout.txt -outputverboselevel 3 to the
distribution agent command. C:\sqlout.txt did not get created.

It worked fine up to a couple of days ago. I'm not sure exactly what
caused the problem, as I made a few changes at the same time. The
changes included: adding a new transactional publication, adding more
articles to an existing transaction publication, and adding a merge
publication. I've tried to go back to the set up before I made the
changes, even disabling replication and starting again from scratch.
Still the problem persists.

The owner of the distribution agent has dbo permissions in both the
publishing and subscribing database. Under 'Publisher and Distributor
Properties' I've set the 'Replication Agent Connection to Publisher'
and 'Agent Connection to the Subscriber' both to Use SQL Server
Authentication, both with the same account that has dbo permissions in
both publishing and subscribing database.

Has anybody come across this problem before? Can anybody make any
suggestions? Thanks in advance for your help.

Regards

Damian Helme
IS Manager
INTEC Engineering (UK) Ltd."Damian H" <damianhelme@.hotmail.com> wrote in message
news:2b893e38.0407222337.542a5fd1@.posting.google.c om...
> Hi,
> For some magical reason, my database replication has suddenly stopped
> working. I modified the publication but the Distribution agent will
> not run; the snapshot does not get applied to the subscriber, and
> changes made at the publisher do not get replicated.
>
> My configuration is: Transactional Replication with a 'Pull'
> Subscription. The Subscriber is Updateable with Immediate Updates
> Only. All created via the SQL Server Enterprise Manager. Both the
> Publisher and Subscriber are on the same server. I'm running SQL
> Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).
> I manually run the snapshop agent. It runs fine with the status
> 'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
> generated'.
> When I look at the distribution agent, things start to get a bit
> confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
> <SERVERNAME?>/ Publication/ Subscription), the status stays
> constantly at 'Never Started'. All other columns are either blank or
> 0. When I right click over the subscription, both Start Synchronising
> and Stop Synchronising are NOT greyed out. If I click on either Start
> Synchronising or Stop Synchronising (absolutely) nothing happens
> (except the mouse turns 'busy' for a fraction of a second). There are
> no error messages.
> I added -output c:\sqlout.txt -outputverboselevel 3 to the
> distribution agent command. C:\sqlout.txt did not get created.
> It worked fine up to a couple of days ago. I'm not sure exactly what
> caused the problem, as I made a few changes at the same time. The
> changes included: adding a new transactional publication, adding more
> articles to an existing transaction publication, and adding a merge
> publication. I've tried to go back to the set up before I made the
> changes, even disabling replication and starting again from scratch.
> Still the problem persists.
> The owner of the distribution agent has dbo permissions in both the
> publishing and subscribing database. Under 'Publisher and Distributor
> Properties' I've set the 'Replication Agent Connection to Publisher'
> and 'Agent Connection to the Subscriber' both to Use SQL Server
> Authentication, both with the same account that has dbo permissions in
> both publishing and subscribing database.
> Has anybody come across this problem before? Can anybody make any
> suggestions? Thanks in advance for your help.
> Regards
> Damian Helme
> IS Manager
> INTEC Engineering (UK) Ltd.

You might want to post this in microsoft.public.sqlserver.replication, as
you may get a better answer over there.

Simon

Replication Distribution Agent cpu continues to grow

We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.com
On Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?
|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com
|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>
|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1

Replication Distribution Agent cpu continues to grow

We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cp
u.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.comOn Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over
a
> million cpu and continued to grow until I stopped and restarted the the pu
ll
> subscription agent on the distribution server. Then it went down to about
a
> hundred cpu. As I'm writing this article its already up to three thousand
cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from maste
r.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million fo
r
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1sql

Replication Distribution Agent cpu continues to grow

We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
--
Message posted via http://www.sqlmonster.comOn Mar 1, 1:39 pm, "fnadal via SQLMonster.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.sqlmonster.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber. Yesterday
>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
--
Message posted via http://www.sqlmonster.com|||That is a cumulative value since the connection started, not an immediate
usage value.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via SQLMonster.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber.
>> Yesterday
>>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
> --
> Message posted via http://www.sqlmonster.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:
>That is a cumulative value since the connection started, not an immediate
>usage value.
>> The cpu usage. When I do a select spid,loginame,program_name, cpu from
>> master.
>[quoted text clipped - 12 lines]
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1

Replication Deadlocks

Hello,
I am running multiple replication publication on a SQL 2k database, with
a separate server as distribution agent, then finally push subscriptions
to multiple databases across 5 servers.
All publications use row and column filtering in them.
My question is, can I use locking hints on the selection criteria for
the row filtering?
ie. Can I specify WITH (NOLOCK) on the row filtering so that it
eliminates the majority of the blocking / deadlocks?
Thanks
Dave
*** Sent via Developersdex http://www.codecomments.com ***
You could if it was a subquery. Do you have indexes on the join
condition/filter key in your filter?
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
"Dave" <Anonymous@.devdex.com> wrote in message
news:eqm8zv1THHA.5060@.TK2MSFTNGP02.phx.gbl...
>
> Hello,
> I am running multiple replication publication on a SQL 2k database, with
> a separate server as distribution agent, then finally push subscriptions
> to multiple databases across 5 servers.
> All publications use row and column filtering in them.
> My question is, can I use locking hints on the selection criteria for
> the row filtering?
> ie. Can I specify WITH (NOLOCK) on the row filtering so that it
> eliminates the majority of the blocking / deadlocks?
> Thanks
> Dave
> *** Sent via Developersdex http://www.codecomments.com ***
|||There is an index on the originating table/column, but the deadlocking
appears to be happening on the distribution database.
David
*** Sent via Developersdex http://www.codecomments.com ***

Replication Clean Up of Failed Server

On my distribution server, I have a failed replication (the big red X) for a
server that had hardware failure a couple of weeks ago. We were able to
bring this client up on a separate server and have re-replicated them. Now
I need to get rid of the failed replication however when I try to simply
delete it, it obviously cannot connect to the failed server since it doesn't
exist and therefore will not delete the information from the DISTRIBUTOR.
I would like to avoid manual system table clean up unless someone has the
method that will completely remove this information.
Is there a way to do this correctly?
Thanks,
Adam P. Cassidy
Did you follow these instructions?
http://support.microsoft.com/kb/324401
Also on your distributor you may have to issue a call to
sp_dropdistpublisher
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
"Adam Patrick Cassidy" <apcassidy@.aol.com> wrote in message
news:OnM$cTvaHHA.2436@.TK2MSFTNGP06.phx.gbl...
> On my distribution server, I have a failed replication (the big red X) for
> a
> server that had hardware failure a couple of weeks ago. We were able to
> bring this client up on a separate server and have re-replicated them.
> Now
> I need to get rid of the failed replication however when I try to simply
> delete it, it obviously cannot connect to the failed server since it
> doesn't
> exist and therefore will not delete the information from the DISTRIBUTOR.
> I would like to avoid manual system table clean up unless someone has the
> method that will completely remove this information.
> Is there a way to do this correctly?
> Thanks,
>
> Adam P. Cassidy
>

Replication and distribution: Agents

Hi all replication experts...

I have created transactional replication on my servers (production server and backup server) and created pull subscription at the backup server. On my production server that also is a distributor and publisher there exist two agents, Snapshot agent and Log reader in the Publishers folder under replication Monitor.

There are also another agent with the backup server name and database name: BackServ:DBName having the type Pull and 'No replicated transactions are available' as Last Action. My question is: What is this? Must it be there?

Grateful for answers

Best,
/M

Its hard to say exactly what this is, but it appears to be your distribution agent. You appear to have a pull agent configured on your subscriber.

It is essential for your transactional replication topology. Do not remove it.

Hilary

|||OK, thanks :)

Replication 2000 - What if Publisher dead

What if a Publication and Distribution server machine fail to work. Do I need to reinitiliaze the whole snapshot on a new machine and retransmit the data to the subscriber. Or can I make use of replication script to recreate the publication and distribution and then replicate to existing subscriber using same machine name?

ThanksHow bad did it fail?|||Let say, if unable to load the SCSI hardisk, or the hardware failured.
Thanks

Originally posted by joejcheng
How bad did it fail?

Replication - distribution agents?

When distribution is scheduled to run at specific times for specific user, but that user is not connected to the server. Distribution tries to find that subscription, the error comes back:

The step was retried the requested number of times(10) without succeeding.

Where/how can I change the requested number to try two or three times.

My problem is that it takes 10-15 minutes for those re-trys and which sometimes causes overlap with the next subscription coming in.Check sp_update_jobstep in BOL, look for @.retry_attempts and @.retry_interval
The best way would be to use a PULL subscription at the subscriber instead of PUSH at the publisher.

Originally posted by cruzin
When distribution is scheduled to run at specific times for specific user, but that user is not connected to the server. Distribution tries to find that subscription, the error comes back:

The step was retried the requested number of times(10) without succeeding.

Where/how can I change the requested number to try two or three times.

My problem is that it takes 10-15 minutes for those re-trys and which sometimes causes overlap with the next subscription coming in.|||You can also identify the job in Enterprise Manager (Management->SQL Server Agent-> Jobs) then find the step and change the retry attempts there.

Originally posted by dbadelphes
Check sp_update_jobstep in BOL, look for @.retry_attempts and @.retry_interval
The best way would be to use a PULL subscription at the subscriber instead of PUSH at the publisher.

Replication

Hi!

I'm trying to implement a transactional replication
with SQL Server 2000. I'm new on this issue. ;)

I tried to configure the distribution, but i received a message, that i didn't understand and that i send you in attachment.

Could you, please, tellme what does it means? And what should be done?

Thank's in advanced

My best regards

siffAs the message says, you must change the SQL Server Agent account (service). Use a domain account that gives you access to the replication folders.
The Snapshot Agent must be able to connect to the publication database on the Publisher and the distribution database on the Distributor. By default on Windows 2000, the snapshot folder used for replication is located at C:\Program Files\Microsoft SQL Server\Mssql\Repldata on the distributor. Each Snapshot Agent must have full control access to this folder. By default on W2000, the replication agents run in the security context of SQL Server Agent domain user account. If the domain user account is not member of the local Administrators group on the Distributor, you should create a shere for the snapshot folder and grant necessary permissions to the share to the domain account under which these replication agents run.

Originally posted by siff
Hi!

I'm trying to implement a transactional replication
with SQL Server 2000. I'm new on this issue. ;)

I tried to configure the distribution, but i received a message, that i didn't understand and that i send you in attachment.

Could you, please, tellme what does it means? And what should be done?

Thank's in advanced

My best regards

siff|||Can u give more details on server roles. Servers involved and their roles (Publisher, Distributor and Subscriber). Are they part of domain / work group etc.

If the servers are part of same domain, add a domain account to the local admin group of server and use that account to run the Sql server agent

If the servers are part of work group then u need to create trusted user connection between the servers.

Replicating SQL dB with exchange 2003

How kan i,
Replicating e-mail addresses, fax numbers and
Distribution Groups from sql database to Ms Exchange 2003?
Kind regardsHi
Look at MSDN for information on WebDAV. Lots of programming work, but that
is the only direct solution.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"HY" <HY@.discussions.microsoft.com> wrote in message
news:5402E527-5324-4D1E-AEBD-9468B7F4361A@.microsoft.com...
> How kan i,
> Replicating e-mail addresses, fax numbers and
> Distribution Groups from sql database to Ms Exchange 2003?
> Kind regards