Showing posts with label publisher. Show all posts
Showing posts with label publisher. Show all posts

Thursday, March 8, 2012

Cannot update replication once live - have to recreate!

I have set up a transactional replication from SQL2000 (W2K) to SQL2005
(W2K3). Once it's running, if I add a new field to the publisher, it doesn't
appear in the subscriber tables. I have tried everything including
re-inititalising the job, stopping and starting agents - nothing works. All I
am left with is deleting then recreating the entire replication job which is
time consuming and annoying.
Somebody out there must have the answer to me inadequacy!
Thanks in advance,
Will, Leeds UK
Will,
I need to understand how you did this. How did you add the new field? Did
you use sp_repladdcolumn?
Also, when you say reinitializing the job I'm not sure what you mean. Do you
mean restart the snapshot agent? If so, this is not reinitialization. If the
subscription is marked for reinitialization, this is something different.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi, basically we replicate live databases onto a separate server for
reporting. Occasionally we modify the live database (add a new field say) and
need the replication job to reflect this change. At the moment, every time we
make a change we have to remove replication, delete the reporting database
copy, then re-add replication. The live databases are on SQL 2000 and
reporting copies on SQL2005.
I haven't tried sp_repladdcolumn yet. I have just been using various actions
from SQL Management Studio.
I am a little confused as to the 'official method' to achieve what I want!
What I do know is that our current method works BUT is very tedious...
Thanks
Will
"Paul Ibison" wrote:

> Will,
> I need to understand how you did this. How did you add the new field? Did
> you use sp_repladdcolumn?
> Also, when you say reinitializing the job I'm not sure what you mean. Do you
> mean restart the snapshot agent? If so, this is not reinitialization. If the
> subscription is marked for reinitialization, this is something different.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>

Wednesday, March 7, 2012

Cannot Subscribe Using Windows Synchronization Manager

Hi,
I'm using two instances of SQL Server 2005 Developer Edition (SP2) on the
same machine. One instance is Publisher and Distributor and the other is
Subscriber. When I try to use Windows Synchronization Manager to subscribe
to the publication, I get this error:
The SQL Server publication uses features that the current version of the
Subscriber does not support. The subscriber should be upgraded to 'Unknown
version of Microsoft SQL Server'.
Any help would be greatly appreciated,
Leila
Can you check the compatibility level of the subscription database?
Also see if you can do a simple pull subscription to see if that works.
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
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23ESWMUCTHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I'm using two instances of SQL Server 2005 Developer Edition (SP2) on the
> same machine. One instance is Publisher and Distributor and the other is
> Subscriber. When I try to use Windows Synchronization Manager to subscribe
> to the publication, I get this error:
> The SQL Server publication uses features that the current version of the
> Subscriber does not support. The subscriber should be upgraded to 'Unknown
> version of Microsoft SQL Server'.
> Any help would be greatly appreciated,
> Leila
>
|||compatibility level is 9, pull subscription without Synchronization Manager
works!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%234mNP4DTHHA.4404@.TK2MSFTNGP03.phx.gbl...
> Can you check the compatibility level of the subscription database?
> Also see if you can do a simple pull subscription to see if that works.
> --
> 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
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23ESWMUCTHHA.1200@.TK2MSFTNGP02.phx.gbl...
>
|||Sounds like something is wrong with Windows Synchronization Manager. Can you
try from another machine?
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
"Leila" <Leilas@.hotpop.com> wrote in message
news:OJC3wRFTHHA.4956@.TK2MSFTNGP04.phx.gbl...
> compatibility level is 9, pull subscription without Synchronization
> Manager works!
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%234mNP4DTHHA.4404@.TK2MSFTNGP03.phx.gbl...
>
|||I'll try that!
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23OP$xzFTHHA.5108@.TK2MSFTNGP06.phx.gbl...
> Sounds like something is wrong with Windows Synchronization Manager. Can
> you try from another machine?
> --
> 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
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:OJC3wRFTHHA.4956@.TK2MSFTNGP04.phx.gbl...
>
|||I'll try that!
One more thing: BOL says that interactive conflict resolution is not
available when you synchronize via SSMS. Then why is there such an option
when you create the subscription in SSMS?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23OP$xzFTHHA.5108@.TK2MSFTNGP06.phx.gbl...
> Sounds like something is wrong with Windows Synchronization Manager. Can
> you try from another machine?
> --
> 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
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:OJC3wRFTHHA.4956@.TK2MSFTNGP04.phx.gbl...
>
|||It is for subscriptions that you will pull through WSM. Note you have to
also enable interactive conflict resolution in WSM as well
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
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23w5nP4HTHHA.2124@.TK2MSFTNGP06.phx.gbl...
> I'll try that!
> One more thing: BOL says that interactive conflict resolution is not
> available when you synchronize via SSMS. Then why is there such an option
> when you create the subscription in SSMS?
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23OP$xzFTHHA.5108@.TK2MSFTNGP06.phx.gbl...
>
>

Friday, February 10, 2012

Cannot replicate non dbo table when dbo table exists

I attempt to replicate a non dbo table, e.g. user1.table1. In the mean time
dbo.table1 exists in both publisher and subscriber and is replicated. When
the replication ran, it drop the dbo.table1 in subscriber and created new
dbo.table1 from user1.table1. How do I replicate non dbo tables when dbo
tables with same names exist?
Thanks!
right click on your publication, select properties, click on the articles
tab, click the browse button, in the general tab make sure that the
destination owner name is the name of the owner you want on the subscriber.
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
"Charts" <Acharts@.newsgroup.nospam> wrote in message
news:FDF72545-7875-491E-B51F-9CECEE79FB4C@.microsoft.com...
>I attempt to replicate a non dbo table, e.g. user1.table1. In the mean
>time
> dbo.table1 exists in both publisher and subscriber and is replicated. When
> the replication ran, it drop the dbo.table1 in subscriber and created new
> dbo.table1 from user1.table1. How do I replicate non dbo tables when dbo
> tables with same names exist?
> Thanks!
>
|||Thanks so much and I'll follow up.
"Charts" wrote:

> I attempt to replicate a non dbo table, e.g. user1.table1. In the mean time
> dbo.table1 exists in both publisher and subscriber and is replicated. When
> the replication ran, it drop the dbo.table1 in subscriber and created new
> dbo.table1 from user1.table1. How do I replicate non dbo tables when dbo
> tables with same names exist?
> Thanks!
>