Q: Push vs. Pull Transactional Replication
We are currently utilizing a push transactional
replication of a subset of the tables in a production
database involving 3 machines; the publisher which is our
production db machine with 4 hyperthreaded processors, 8
GB ram, a distribution db machine with 1 processor, 2 GB
ram, and a subscriber db machine with 2 hyperthreaded
processors, 6 GB ram to which this table subset is
replicated. All machines are SQL EE with SP3. The
subscriber is used for complex searches and has 6 indexed
views resident on it. All replication agents are set to
run continuously.
The Distribution Agent profiles have been left at the
defaults except for QueryTimeout, which has been set to
3600.
Because we cannot simulate this environment for testing,
I would appreciate hearing from anyone who has experience
with a push vs. pull subscription from a performance
standpoint. Thanks very much for your input.
pull offloads the distribution agent to the subscriber. Hence your
performance on your publisher is better.
The problem is that then you no longer have a central point of
administration - in other words you manage your publications and snapshot
agent on your publisher, but your distribution agent on your subscriber.
I can't quantify exactly what performance increase you will have on your
publisher as it is largely a function of load and hardware on your publisher
and subscriber.
You will have to test to see what performance increase you get. You can get
an idea of what it will be by stopping your log reader and distribution
agent on your publisher.
"fundster" <anonymous@.discussions.microsoft.com> wrote in message
news:98dc01c433b2$498477f0$a301280a@.phx.gbl...
> Q: Push vs. Pull Transactional Replication
> We are currently utilizing a push transactional
> replication of a subset of the tables in a production
> database involving 3 machines; the publisher which is our
> production db machine with 4 hyperthreaded processors, 8
> GB ram, a distribution db machine with 1 processor, 2 GB
> ram, and a subscriber db machine with 2 hyperthreaded
> processors, 6 GB ram to which this table subset is
> replicated. All machines are SQL EE with SP3. The
> subscriber is used for complex searches and has 6 indexed
> views resident on it. All replication agents are set to
> run continuously.
> The Distribution Agent profiles have been left at the
> defaults except for QueryTimeout, which has been set to
> 3600.
> Because we cannot simulate this environment for testing,
> I would appreciate hearing from anyone who has experience
> with a push vs. pull subscription from a performance
> standpoint. Thanks very much for your input.
>
|||I would think that you would not need to stop the log reader. Even with a
pull subscription the log reader is still running on the publisher.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||that's a very good point Rand, I missed that.
I was trying to get a baseline "without" replication, but to get a
representative baseline with pull subscriptions you really should have the
log reader agent running.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:nxrqWlENEHA.3780@.cpmsftngxa10.phx.gbl...
> I would think that you would not need to stop the log reader. Even with a
> pull subscription the log reader is still running on the publisher.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
sql
Showing posts with label transactional. Show all posts
Showing posts with label transactional. Show all posts
Monday, March 26, 2012
Push Subscription Connection Fails
I cannot get internet connection to work for push subscription to transactional publication.
Publisher/distributor: SQL Server 2000
Subscriber: SQL Server 2000
Connection: TCP/IP, SQL Authentication. Works fine from SQLEM or Query Analyzer.
Subscription: push, transactional, schema/data already initialized.
When I run distributor agent fails with "The process could not connect to subscriber 'TEST'", error "Server does not exist or access denied".
Agent output does not give anything more specific. It fails after...
Connecting to Subscriber 'TEST'
Connecting to Subscriber 'TEST.REPL'
Profiler shows nothing happening at all.
If change subscriber setup on distributor to use trusted connection instead of SQL Auth it works fine.
Any ideas?OK, so all the replication experts are on vacation this week but I eventually managed to figure it out myself.
When defining subscribers (through 'distributor properties') use the subscriber TCP/IP address directly and not a server alias like I was doing. Silly Billy!
Publisher/distributor: SQL Server 2000
Subscriber: SQL Server 2000
Connection: TCP/IP, SQL Authentication. Works fine from SQLEM or Query Analyzer.
Subscription: push, transactional, schema/data already initialized.
When I run distributor agent fails with "The process could not connect to subscriber 'TEST'", error "Server does not exist or access denied".
Agent output does not give anything more specific. It fails after...
Connecting to Subscriber 'TEST'
Connecting to Subscriber 'TEST.REPL'
Profiler shows nothing happening at all.
If change subscriber setup on distributor to use trusted connection instead of SQL Auth it works fine.
Any ideas?OK, so all the replication experts are on vacation this week but I eventually managed to figure it out myself.
When defining subscribers (through 'distributor properties') use the subscriber TCP/IP address directly and not a server alias like I was doing. Silly Billy!
Monday, March 12, 2012
Pull Subscription for transactional replication
I have setup a pull subscription on the subscriber for transactional replication. The distribution job continues to run, but doesn't do anything because it says: The initial snapshot for publication 'man4' is not yet available.
How can I tell if the snapshot is running, and can I see the snapshot where it was created?The snapshot is set up on the publisher and must be created before any subscriptions are set up.
How can I tell if the snapshot is running, and can I see the snapshot where it was created?The snapshot is set up on the publisher and must be created before any subscriptions are set up.
Friday, March 9, 2012
publishing a subscription ( 3 servers )
I have a publisher that publishes a subset of master data ( transactional ).
The subscriber then publishes the same tables to dumb, live servers.
Transactional again. The master server ( the first one in the chain) is the
distributor. Replication is initiated via the Replication ActiveX objects
from a .NET application.
Once I have applied the snapshots in order and configured the servers,
replication breaks after about a day with errors about not being able to
drop tables on the intermediate server because they are participating in
replication. No surprise about the error, except since I am using
transactional replication everywhere, why is it trying to drop the table?
it is a push-only publication, I do not need merge replication, conflict
resolution, or updating from the subscriber. How can I prevent my error.
Surely what I want to do can't be so unusual?
Think Content Management Systems.
Admin database -> publishes to - > staging database -> publishes to -> live
database.
This should be straight-forward, no?
thanks for any help guys.
Leon
Leon,
your @.pre_creation_cmd is drop. If you create the first publication and
subscription then set it going (initialize it), then create the second one -
the republisher, it should be ok. You will have problems if you need to
reinitialize the first publisher/subscriber pair and will receive the
message you saw, so in this case you'll first need to drop the second
publication, and readd it later.
HTH,
Paul Ibison
|||( whoops - must remember to Reply Group!! )
thanks Paul. I know this happens when I run the initial snapshot, and I
create the publications very carefully as a result ( I ran a generate sql on
the pubs to save time )
The first time I set this up, everything was fine, except I needed to drop
and recreate the second publication on account of a change in configuration.
then the problems started. It all works fine for about half a day, then I
get the error - so I wonder if I haven't properly removed the publications
that first time... I'm going to clear everything, diable replication and run
from a clean slate here, and keep in mind what you're saying. Lucky that I
can eh!
Are there any other gotchas I need to be aware of when re-publishing a
subscribed table?
Thanks again
Leon
-- Original Message --
From: "Paul Ibison" <Paul.Ibison@.Pygmalion.Com>
Newsgroups: microsoft.public.sqlserver.replication
Sent: Monday, May 17, 2004 11:00 AM
Subject: Re: publishing a subscription ( 3 servers )
> Leon,
> your @.pre_creation_cmd is drop. If you create the first publication and
> subscription then set it going (initialize it), then create the second
one -
> the republisher, it should be ok. You will have problems if you need to
> reinitialize the first publisher/subscriber pair and will receive the
> message you saw, so in this case you'll first need to drop the second
> publication, and readd it later.
> HTH,
> Paul Ibison
>
|||I think you need to
1) script out the schema you want replicated on your publisher, run it on the first subscriber/publisher and the second subscriber
2) when you create your publication on both your publisher and subscriber/publisher in the article properties selection delete all the data in the existing table in the name conflicts section.
3) create your publication and subscription from your publisher to your publisher subscriber.
4) generate your snapshot and replicate it from your publisher to your publisher/susbcriber.
5) when 4 is complete, repeat steps 3 and 4 for your publisher/subscriber to your subscriber.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
The subscriber then publishes the same tables to dumb, live servers.
Transactional again. The master server ( the first one in the chain) is the
distributor. Replication is initiated via the Replication ActiveX objects
from a .NET application.
Once I have applied the snapshots in order and configured the servers,
replication breaks after about a day with errors about not being able to
drop tables on the intermediate server because they are participating in
replication. No surprise about the error, except since I am using
transactional replication everywhere, why is it trying to drop the table?
it is a push-only publication, I do not need merge replication, conflict
resolution, or updating from the subscriber. How can I prevent my error.
Surely what I want to do can't be so unusual?
Think Content Management Systems.
Admin database -> publishes to - > staging database -> publishes to -> live
database.
This should be straight-forward, no?
thanks for any help guys.
Leon
Leon,
your @.pre_creation_cmd is drop. If you create the first publication and
subscription then set it going (initialize it), then create the second one -
the republisher, it should be ok. You will have problems if you need to
reinitialize the first publisher/subscriber pair and will receive the
message you saw, so in this case you'll first need to drop the second
publication, and readd it later.
HTH,
Paul Ibison
|||( whoops - must remember to Reply Group!! )
thanks Paul. I know this happens when I run the initial snapshot, and I
create the publications very carefully as a result ( I ran a generate sql on
the pubs to save time )
The first time I set this up, everything was fine, except I needed to drop
and recreate the second publication on account of a change in configuration.
then the problems started. It all works fine for about half a day, then I
get the error - so I wonder if I haven't properly removed the publications
that first time... I'm going to clear everything, diable replication and run
from a clean slate here, and keep in mind what you're saying. Lucky that I
can eh!
Are there any other gotchas I need to be aware of when re-publishing a
subscribed table?
Thanks again
Leon
-- Original Message --
From: "Paul Ibison" <Paul.Ibison@.Pygmalion.Com>
Newsgroups: microsoft.public.sqlserver.replication
Sent: Monday, May 17, 2004 11:00 AM
Subject: Re: publishing a subscription ( 3 servers )
> Leon,
> your @.pre_creation_cmd is drop. If you create the first publication and
> subscription then set it going (initialize it), then create the second
one -
> the republisher, it should be ok. You will have problems if you need to
> reinitialize the first publisher/subscriber pair and will receive the
> message you saw, so in this case you'll first need to drop the second
> publication, and readd it later.
> HTH,
> Paul Ibison
>
|||I think you need to
1) script out the schema you want replicated on your publisher, run it on the first subscriber/publisher and the second subscriber
2) when you create your publication on both your publisher and subscriber/publisher in the article properties selection delete all the data in the existing table in the name conflicts section.
3) create your publication and subscription from your publisher to your publisher subscriber.
4) generate your snapshot and replicate it from your publisher to your publisher/susbcriber.
5) when 4 is complete, repeat steps 3 and 4 for your publisher/subscriber to your subscriber.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Wednesday, March 7, 2012
Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin
I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin
I have a wired situation..!
sql jobs related to the replication. When I changed the name back to
what it was, and now I can see the replication tree under the
replication Monitor window...
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..Has anyone seen this issue? Any thoughts? Thanks in advance..
Query Builder wrote:
Quote:
Originally Posted by
I have a wired situation..!
>
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
>
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
>
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
>
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
>
All it says is (No Items)...
>
I would appreciate any help to correct this issue... Thanks in advance..
sql jobs related to the replication. When I changed the name back to
what it was, and now I can see the replication tree under the
replication Monitor window...
Query Builder wrote:
Quote:
Originally Posted by
Has anyone seen this issue? Any thoughts? Thanks in advance..
>
>
Query Builder wrote:
Quote:
Originally Posted by
I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin
I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Yes, I do see the publications under the Replication --> Publication
tab. I can also confirm that the replication is working as it is
pushing those updates to the subscriber. I am unable to run the
sp_MSload_replication_status as it is returning the following error..
Server: Msg 8152, Level 16, State 6, Procedure
sp_MSload_replication_status, Line 19
String or binary data would be truncated.
The statement has been terminated.
Thanks for the update. I would appreciate if you can help me figure out
the issue...
Thanks again..
On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> You could try running sp_MSload_replication_status.
> To investigate further I'd like to know if you see the publication under the
> "Replication" folder and/or the "Publications" folder in the published
> database.
> Also, there was an issue with this prior to sp4
> (http://support.microsoft.com/kb/814032) so please ensure that you've got
> the latest sp.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > You could try running sp_MSload_replication_status.
> > To investigate further I'd like to know if you see the publication under the
> > "Replication" folder and/or the "Publications" folder in the published
> > database.
> > Also, there was an issue with this prior to sp4
> > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > the latest sp.
> > Cheers,
> > Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
> > Yes, I do see the publications under the Replication --> Publication
> > tab. I can also confirm that the replication is working as it is
> > pushing those updates to the subscriber. I am unable to run the
> > sp_MSload_replication_status as it is returning the following error..
> >
> > Server: Msg 8152, Level 16, State 6, Procedure
> > sp_MSload_replication_status, Line 19
> > String or binary data would be truncated.
> > The statement has been terminated.
> >
> > Thanks for the update. I would appreciate if you can help me figure out
> > the issue...
> >
> > Thanks again..
> >
> >
> > On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > > You could try running sp_MSload_replication_status.
> > > To investigate further I'd like to know if you see the publication under the
> > > "Replication" folder and/or the "Publications" folder in the published
> > > database.
> > > Also, there was an issue with this prior to sp4
> > > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > > the latest sp.
> > > Cheers,
> > > Paul Ibison SQL Server MVP,www.replicationanswers.com.
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||Yes, I do see the publications under the Replication --> Publication
tab. I can also confirm that the replication is working as it is
pushing those updates to the subscriber. I am unable to run the
sp_MSload_replication_status as it is returning the following error..
Server: Msg 8152, Level 16, State 6, Procedure
sp_MSload_replication_status, Line 19
String or binary data would be truncated.
The statement has been terminated.
Thanks for the update. I would appreciate if you can help me figure out
the issue...
Thanks again..
On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> You could try running sp_MSload_replication_status.
> To investigate further I'd like to know if you see the publication under the
> "Replication" folder and/or the "Publications" folder in the published
> database.
> Also, there was an issue with this prior to sp4
> (http://support.microsoft.com/kb/814032) so please ensure that you've got
> the latest sp.
> Cheers,
> Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > You could try running sp_MSload_replication_status.
> > To investigate further I'd like to know if you see the publication under the
> > "Replication" folder and/or the "Publications" folder in the published
> > database.
> > Also, there was an issue with this prior to sp4
> > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > the latest sp.
> > Cheers,
> > Paul Ibison SQL Server MVP,www.replicationanswers.com.|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:
> > Yes, I do see the publications under the Replication --> Publication
> > tab. I can also confirm that the replication is working as it is
> > pushing those updates to the subscriber. I am unable to run the
> > sp_MSload_replication_status as it is returning the following error..
> >
> > Server: Msg 8152, Level 16, State 6, Procedure
> > sp_MSload_replication_status, Line 19
> > String or binary data would be truncated.
> > The statement has been terminated.
> >
> > Thanks for the update. I would appreciate if you can help me figure out
> > the issue...
> >
> > Thanks again..
> >
> >
> > On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
> > > You could try running sp_MSload_replication_status.
> > > To investigate further I'd like to know if you see the publication under the
> > > "Replication" folder and/or the "Publications" folder in the published
> > > database.
> > > Also, there was an issue with this prior to sp4
> > > (http://support.microsoft.com/kb/814032) so please ensure that you've got
> > > the latest sp.
> > > Cheers,
> > > Paul Ibison SQL Server MVP,www.replicationanswers.com.
Publisher goes down - Replication
What happens when Publisher goes down in Transactional
Replication, no corruption (power , hardware failure)??
Thanks,
JohnWhen publisher goes down, stop all subscriptions and the distributor before you restart the publiser. Once the publisher got restarted, start the distributor and the subscription. You may need to resync, because the distributor may not have the right sequence number.
Replication, no corruption (power , hardware failure)??
Thanks,
JohnWhen publisher goes down, stop all subscriptions and the distributor before you restart the publiser. Once the publisher got restarted, start the distributor and the subscription. You may need to resync, because the distributor may not have the right sequence number.
Subscribe to:
Posts (Atom)