Showing posts with label helloi. Show all posts
Showing posts with label helloi. Show all posts

Monday, March 26, 2012

Merge replication with alternate synchoronization partner

Hello:
I have a merge replication and I defined a Publisher A as a primary
publisher and distributor, a Publisher B as an alternate synchronization
partner and distributor and a subscriber to the Publisher A.
We need to turn off the server which is Publisher A and set the Publiser B
as the alternate partner so we can replicate data between Publisher B and
the subscriber even if Publiser A if off.
I followed the following procedure:
-From the Pusbliser A I go to SQL Server agents, Jobs and then modify the
job that is PublisherA-SubscriberA. Modify the commad box to the PublisherB
and the parameter SyncToAlternate 1.
-Re-Start the merge agent
I get the error "The process could not drop one or more tables because the
tables are being used by other publications. The step failed"
Do I need to modify something else? What can I do? Because we need to turn
off the Publisher A and the replication still going between the other two
servers.
Thanks in advance
Jennyfer Barco
did you follow the steps outlined in
http://support.microsoft.com/default...roduct=sql2k#3
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:uwsCF6VkEHA.3756@.TK2MSFTNGP11.phx.gbl...
> Hello:
> I have a merge replication and I defined a Publisher A as a primary
> publisher and distributor, a Publisher B as an alternate synchronization
> partner and distributor and a subscriber to the Publisher A.
> We need to turn off the server which is Publisher A and set the Publiser B
> as the alternate partner so we can replicate data between Publisher B and
> the subscriber even if Publiser A if off.
> I followed the following procedure:
> -From the Pusbliser A I go to SQL Server agents, Jobs and then modify the
> job that is PublisherA-SubscriberA. Modify the commad box to the
PublisherB
> and the parameter SyncToAlternate 1.
> -Re-Start the merge agent
> I get the error "The process could not drop one or more tables because the
> tables are being used by other publications. The step failed"
> Do I need to modify something else? What can I do? Because we need to turn
> off the Publisher A and the replication still going between the other two
> servers.
> Thanks in advance
> Jennyfer Barco
>
|||Yes, I set up the suscriber following the directions and now the three
servers are replicating OK. Because we need to turn off the PubliserA I
followed the options under "Use SQL Server Enterprise Manager to Synchronize
with Alternate Synchronization Partner" but when I started synch I get the
error. I'm doing these steps from the Publisher A. Is it OK? Is there
anything else Ineed to do?
Thanks so much
Jennyfer
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e4N1Y4akEHA.3428@.TK2MSFTNGP11.phx.gbl...
> did you follow the steps outlined in
>
http://support.microsoft.com/default...roduct=sql2k#3[vbcol=seagreen]
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
> news:uwsCF6VkEHA.3756@.TK2MSFTNGP11.phx.gbl...
B[vbcol=seagreen]
and[vbcol=seagreen]
the[vbcol=seagreen]
> PublisherB
the[vbcol=seagreen]
turn[vbcol=seagreen]
two
>
|||Yes, I set up the suscriber following the directions and now the three
servers are replicating OK. Because we need to turn off the PubliserA I
followed the options under "Use SQL Server Enterprise Manager to Synchronize
with Alternate Synchronization Partner" but when I started synch I get the
error. I'm doing these steps from the Publisher A. Is it OK? Is there
anything else I need to do?
Thanks so much
Jennyfer
"Jennyfer J Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:esne3BdkEHA.3720@.TK2MSFTNGP12.phx.gbl...
> Yes, I set up the suscriber following the directions and now the three
> servers are replicating OK. Because we need to turn off the PubliserA I
> followed the options under "Use SQL Server Enterprise Manager to
Synchronize
> with Alternate Synchronization Partner" but when I started synch I get the
> error. I'm doing these steps from the Publisher A. Is it OK? Is there
> anything else Ineed to do?
> Thanks so much
> Jennyfer
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e4N1Y4akEHA.3428@.TK2MSFTNGP11.phx.gbl...
>
http://support.microsoft.com/default...roduct=sql2k#3[vbcol=seagreen]
synchronization[vbcol=seagreen]
Publiser
> B
> and
> the
> the
> turn
> two
>

Merge replication trouble

Hello
I have made a merge replication between two server W2k with sql2000 sp3. Those servers are connected via internet. In distributor (also publisher) I have setting up aliases for both servers. Have generated snapshot but when agent run I have this error: -2
147201019 and 14010 : "the subscription for pubblication [bla bla] is invalid".
I have searching in the net some solutions but I have noticed that in all cases it is depended by alias setting. But I have defined its ?
Some ideas ?
Have solved the puzzle.
In subscription I have noticed with sp_helpserver that the subscription server hav id = 1 so have do this:
sp_dropserver 'DIST_SERVER'
sp_dropserver 'SUB_SERVER'
sp_addserver 'SUB_SERVER', @.local = 'LOCAL'
where DIST_SERVER is my distribution, publisher server and SUB_SERVER is my subscription server.
Bests
|||Rafal,
OK, and the last 2 commands will require a restart of the services.
I'm not clear what the first line is for though (sp_dropserver 'DIST_SERVER').
Regards,
Paul Ibison

Wednesday, March 21, 2012

Merge replication publisher subscriber

Hello
I have Publisher and 200 subscribers
I need to unload Publisher having added N intermediate Publishers
on 50 subscribers to everyone
And each intermediate publisher stores data only for it's owns
subscribers.
Is this possible?
Do I need for subscription that are created to be with ' global '
sync_typ?
Is there a particular order in witch a publications and a subscription
are created?
Thanks for your helps
ps : sql2000 SP4,8.00.2187
Yes this is called republishing and it is recommended when you have large
numbers of merge subscribers. It does require the global priority between
the republishers. You create the main publisher first and then the
downstream ones.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"maroucia" <maroucia@.yahoo.com> wrote in message
news:1161252010.072061.165570@.b28g2000cwb.googlegr oups.com...
> Hello
> I have Publisher and 200 subscribers
> I need to unload Publisher having added N intermediate Publishers
> on 50 subscribers to everyone
> And each intermediate publisher stores data only for it's owns
> subscribers.
> Is this possible?
> Do I need for subscription that are created to be with ' global '
> sync_typ?
> Is there a particular order in witch a publications and a subscription
> are created?
> Thanks for your helps
> ps : sql2000 SP4,8.00.2187
>
|||http://www.replicationanswers.com/Republishing2005.asp

Merge replication publisher subscriber

Hello
I have Publisher and 200 subscribers
I need to unload Publisher having added N intermediate Publishers
on 50 subscribers to everyone
And each intermediate publisher stores data only for it's owns
subscribers.
Is this possible?
Do I need for subscription that are created to be with ' global '
sync_typ?
Is there a particular order in witch a publications and a subscription
are created?
Thanks for your helps
ps : sql2000 SP4,8.00.2187Yes this is called republishing and it is recommended when you have large
numbers of merge subscribers. It does require the global priority between
the republishers. You create the main publisher first and then the
downstream ones.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"maroucia" <maroucia@.yahoo.com> wrote in message
news:1161252010.072061.165570@.b28g2000cwb.googlegroups.com...
> Hello
> I have Publisher and 200 subscribers
> I need to unload Publisher having added N intermediate Publishers
> on 50 subscribers to everyone
> And each intermediate publisher stores data only for it's owns
> subscribers.
> Is this possible?
> Do I need for subscription that are created to be with ' global '
> sync_typ?
> Is there a particular order in witch a publications and a subscription
> are created?
> Thanks for your helps
> ps : sql2000 SP4,8.00.2187
>|||http://www.replicationanswers.com/Republishing2005.asp

Merge Replication Problem

Hello
I have merge Replication MSSQL Server 2000 SP4, One Publisher and 5
subscribers,
a) Subscribers1 has inserted the record at 8 AM and Send it to
subscribers2 & subscribers3
b) Using DTS, but not insert directly subscribers2 DB its Inserted
TempDB to subscribers2 DB using Store procedure.
c) Subscribers2 users update same records at 3 PM. It means now other
Subscribers not update those records.
d) I changed my article
@.property='compensate_for_errors',@.value='false'.
e) I have facing some conflict Problems
f) After Synchronization those records was deleted at some
Subscriber
g) We are Synchronization at 1 AM. For Schedule bases
Here the Question.
Why the Data going to deleted?
Which data going to Synchronies in above case?
Suppose I update row 1 following time
Subscribers1 at 6 am
Subscribers1 at 7 am
Subscribers1 at 8 am
Subscribers1 at 9 am
Subscribers1 at 11 am
Which data going to Synchronies in above case?
Please Explaning Clearly
Thanks
Sam
Sam I am having problems understanding the scenario you present. Before I
start guessing at what happened I want to explain a couple of things.
a) compensate_for_errors - this switch means that if a conflict occurs the
data will not be wiped out on the conflict loser. For example if a row with
the same PK value is simultaneously inserted on the publisher and subscriber
and the compensate_for_errors switch is set to true (true is default for SQL
2000, false is the default for SQL 2005) the row on the subscriber will be
deleted and replaced with the row from the publisher. If the
compensate_for_errors setting is set to false, the row on the subscriber
will not be deleted - in other words - the subscribers row will remain.
With this setting all such compensating actions will not occur.
b) when you use DTS with the defaults the rows dts'd into the table are not
logged and will not be replicated. Consult
http://support.microsoft.com/kb/275680/en-us for more information.
c) exactly what do you mean by "Using DTS, but not insert directly
subscribers2 DB its Inserted TempDB to subscribers2 DB using Store
procedure." If you mean it was DTS'd to tempdb and then from tempdb to the
subscriber2 db, this should have been logged and any inserts or other DML as
a result of this action should be replicated.
d) did you run conflict viewer for a window into what is happening?
It sounds like what happened what that in step b the rows were not logged
and hence never made it to subscriber 1 and subscriber 3. I don't understand
what happened in f). The conflict viewer should have a record of what
happened.
To answer your questions - data should not be deleted with the
compensate_for_errors setting set to false - only true.
From what you describe in the below scenario, if you are updating the same
row the update should flow with each synchronization unless you are doing
column level tracking - this would be logged as a conflict and the conflict
winner should win the conflict - ie its data should make it to all the
subscribers.
If the sync doesn't happen each hour, only the final result will travel. For
example if the sync runs at 11 am, only the final 11 am change will move.
HTH
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Sam" <shankar@.cdscom.co.th> wrote in message
news:Os7L2bEOGHA.812@.TK2MSFTNGP10.phx.gbl...
> Hello
> I have merge Replication MSSQL Server 2000 SP4, One Publisher and 5
> subscribers,
> a) Subscribers1 has inserted the record at 8 AM and Send it to
> subscribers2 & subscribers3
> b) Using DTS, but not insert directly subscribers2 DB its Inserted
> TempDB to subscribers2 DB using Store procedure.
> c) Subscribers2 users update same records at 3 PM. It means now other
> Subscribers not update those records.
> d) I changed my article
> @.property='compensate_for_errors',@.value='false'.
> e) I have facing some conflict Problems
> f) After Synchronization those records was deleted at some
> Subscriber
> g) We are Synchronization at 1 AM. For Schedule bases
>
> Here the Question.
> Why the Data going to deleted?
> Which data going to Synchronies in above case?
>
> Suppose I update row 1 following time
> Subscribers1 at 6 am
> Subscribers1 at 7 am
> Subscribers1 at 8 am
> Subscribers1 at 9 am
> Subscribers1 at 11 am
> Which data going to Synchronies in above case?
>
> Please Explaning Clearly
> Thanks
> Sam
>
>
>
>
>
>
>
|||THANKS Hilary
I need to test , let Contact You.
Sam
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:erQqQoHOGHA.2992@.tk2msftngp13.phx.gbl...
> Sam I am having problems understanding the scenario you present. Before I
> start guessing at what happened I want to explain a couple of things.
> a) compensate_for_errors - this switch means that if a conflict occurs the
> data will not be wiped out on the conflict loser. For example if a row
> with the same PK value is simultaneously inserted on the publisher and
> subscriber and the compensate_for_errors switch is set to true (true is
> default for SQL 2000, false is the default for SQL 2005) the row on the
> subscriber will be deleted and replaced with the row from the publisher.
> If the compensate_for_errors setting is set to false, the row on the
> subscriber will not be deleted - in other words - the subscribers row
> will remain. With this setting all such compensating actions will not
> occur.
> b) when you use DTS with the defaults the rows dts'd into the table are
> not logged and will not be replicated. Consult
> http://support.microsoft.com/kb/275680/en-us for more information.
> c) exactly what do you mean by "Using DTS, but not insert directly
> subscribers2 DB its Inserted TempDB to subscribers2 DB using Store
> procedure." If you mean it was DTS'd to tempdb and then from tempdb to the
> subscriber2 db, this should have been logged and any inserts or other DML
> as a result of this action should be replicated.
> d) did you run conflict viewer for a window into what is happening?
> It sounds like what happened what that in step b the rows were not logged
> and hence never made it to subscriber 1 and subscriber 3. I don't
> understand what happened in f). The conflict viewer should have a record
> of what happened.
> To answer your questions - data should not be deleted with the
> compensate_for_errors setting set to false - only true.
> From what you describe in the below scenario, if you are updating the same
> row the update should flow with each synchronization unless you are doing
> column level tracking - this would be logged as a conflict and the
> conflict winner should win the conflict - ie its data should make it to
> all the subscribers.
> If the sync doesn't happen each hour, only the final result will travel.
> For example if the sync runs at 11 am, only the final 11 am change will
> move.
> HTH
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "Sam" <shankar@.cdscom.co.th> wrote in message
> news:Os7L2bEOGHA.812@.TK2MSFTNGP10.phx.gbl...
>

Monday, March 19, 2012

merge replication only need passwrd first time

Hello
I have an applicatiuon on a pda where i can synchronize the pda with
sql server 2000
When I start the application on open the synchronize window i have to
enter a user id and password.
repl.InternetLogin = userId
repl.InternetPassword = Password
I start the synchronization and it works.
The second time i synchronize it still works even with no password.
Why is that? I have to stop the application and start it again for it
to work.
If I enetr a wrong password when I synchronize the first time, I gett e
message saying: Authentication failed on the computer running IIS
I would like to get this message all the time when I synchronize with
an incorrect password.
What can I be doing wrong.
What form of authentication are you using on your IIS Server. Is it possible
that you have a blank password for the account userID?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<jensenove@.netscape.net> wrote in message
news:1144351127.584971.98050@.t31g2000cwb.googlegro ups.com...
> Hello
> I have an applicatiuon on a pda where i can synchronize the pda with
> sql server 2000
> When I start the application on open the synchronize window i have to
> enter a user id and password.
> repl.InternetLogin = userId
> repl.InternetPassword = Password
>
> I start the synchronization and it works.
> The second time i synchronize it still works even with no password.
> Why is that? I have to stop the application and start it again for it
> to work.
> If I enetr a wrong password when I synchronize the first time, I gett e
> message saying: Authentication failed on the computer running IIS
> I would like to get this message all the time when I synchronize with
> an incorrect password.
> What can I be doing wrong.
>

Friday, March 9, 2012

Merge Replication Fail

Hello
I am face the following problem.
Invalid object name 'sysmergearticles'.
The merge replication is falling please help me.
Best regards,
FDB
Is this failure when setting up replication or did it cause the merge agent
to fail suddenly?
Sysmergearticles is an important system table, Did you apply any service
packs patches before you saw this error?
thanks
gopal
|||This failure happen when i setting up replication.
I have SQL Server 2000 Personal Edition SP3.
My server is a subscriber.
"Gopal Ashok [MS]" <gopal@.online.microsoft.net> wrote in message
news:XJjN7gMIEHA.3568@.cpmsftngxa06.phx.gbl...
> Is this failure when setting up replication or did it cause the merge
agent
> to fail suddenly?
> Sysmergearticles is an important system table, Did you apply any service
> packs patches before you saw this error?
> thanks
> gopal
>

Merge replication fail

Hello
I am face the following problem.
Invalid object name 'sysmergearticles'.
The merge replication is falling please help me.
Best regards,
FDB
Are you getting this while deploying your snapshot?
If so go to your publishing database, expand your table collection, right
click on the table sysmergearticles and select copy. go to your subscribing
database, open up isqlw and change to your database, select Edit, Paste,
execute it, and start your merge agent again
"news.microsoft.com" <fabiobarion@.hotmail.com> wrote in message
news:%23Jhjq6$GEHA.2052@.TK2MSFTNGP12.phx.gbl...
> Hello
> I am face the following problem.
> Invalid object name 'sysmergearticles'.
> The merge replication is falling please help me.
> Best regards,
> FDB
>

Saturday, February 25, 2012

Merge Replication between MSDE doesn't work!

Hello!

I have a problem with creating Merge replication between two instances of MSDE 2000. In the article http://support.microsoft.com/kb/324992/, published by Microsoft, described, that it is possible.

I am creating Merge Publication at MSDE 2000, with Distributor and Publisher configured at same machine, with options "Allow Pull Subscriptions" and "Allow Anonymous Subscriptions". There is no problem with creating of Publication. Even snapshot generation finishes successfully. Also I create a login with SQL Server Authentication and "System Administrators" database role at the publisher in order to connect to it from Subscriber.

The problem occurs, when creating anonymous pull subscription to this publication at another instance of MSDE. During initial synchronization an error occurs:

The process could not connect to Distributor '<publisher_server_name>'. Login failed for user '<login_created_at_publisher>'. Reason: Not associated with a trusted SQL Server connection. The step failed.

Although I didn't use Windows Authentication at all, so Subscriber doesn't need to connect to Distributor using trusted SQL Server connection.

What is a problem and how can I workaround?

Note: The same works correctly, if MS SQL Server used as a Publisher instead of MSDE.

Please, help!

I can provide publication and subscription creation scripts, if required.

Guys, don't care anymore: I found the reason!!!

Probably, the problem was in using an old version of MSDE, and installing MSDE with SP4 solved it!

However, there are still some problems with connecting to MSDE from a remote workstation via named pipes, but I think I can research it independently.

Thanks for consideration!