Computer name change at subscriber and Replication fail

Hello,
The computer name of one of the subscribers was changed and now the
sychronization does not go through.
It is not possible to changed back and I would like to know if there is an
easy way to get the subscriber back to work.
Thanks,
car.
Realistically you'll need to reinitialize. You could hack the system tables
if you are on SQL Server 2000 but I wouldn't advise it.
Paul Ibison
|||You need to drop your subscription and recreate it for the new subscriber.
"Car" <Car@.discussions.microsoft.com> wrote in message
news:5F57C2E3-0ADF-4CCE-95DF-A693BF317398@.microsoft.com...
> Hello,
> The computer name of one of the subscribers was changed and now the
> sychronization does not go through.
> It is not possible to changed back and I would like to know if there is an
> easy way to get the subscriber back to work.
> Thanks,
> car.
|||I don't know the kind of replication you're using. But maybe this can help
you.
Now I'm testing the replication that we'll set up in our customer and I've
done this:
Backup a subscription database in computer A.
Copied backup to computer B.
Switched off computer A.
Restore backup in computer B.
Changed name in computer B, setting computer's A name.
Execute:
Use Master
go
Sp_DropServer 'B\INSTANCE_NAME'
GO
Use Master
go
Sp_Addserver 'A\INSTANCE_NAME', 'local'
GO
This works if you have synchronized before doing the backup. I still need to
try if I do the backup before (so the changes are already replicated to
Publisher).
So for this, I think that just executing the script will be enough for you.
But now I'm afraid for what Paul an Hilary has said...
Josep.
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:%23zMmeLqgHHA.3796@.TK2MSFTNGP02.phx.gbl...
> You need to drop your subscription and recreate it for the new subscriber.
> "Car" <Car@.discussions.microsoft.com> wrote in message
> news:5F57C2E3-0ADF-4CCE-95DF-A693BF317398@.microsoft.com...
>

Compressed Snapshot Files!

Hello All,
I'm using Transactional Replication. I have compress snapshot file now I
want to configure it on Subscriber.
I saw BOL and it says,
1. In Microsoft SQL Server Enterprise Manager, expand the subscription
database and the Subscriptions directory, right- click a subscription,
and then click Properties.
but didnt find the Subscription directory under subscription database.
How can I configure?
Thanks in advance.
Naveed.
the snapshot files will be compressed in the cab format in your alternate
snapshot folder. If you are doing a pull subscription you have the option to
applying the snapshot (compressed or uncompressed) from an alternate
location by using the "Use snapshot files from the following folder option."
You will have to prove a path to the root of the snapshot location, ie
\\PublisherServerName\Share\ where this will map to c:\temp or wherever you
place your files in. If you copy these files locally you have to copy the
directory structure from unc on, ie if you place the files in c:\temp you
would copy the contents of unc to c:\temp.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:OoosGusqEHA.2732@.TK2MSFTNGP09.phx.gbl...
> Hello All,
> I'm using Transactional Replication. I have compress snapshot file now I
> want to configure it on Subscriber.
> I saw BOL and it says,
> 1. In Microsoft SQL Server Enterprise Manager, expand the subscription
> database and the Subscriptions directory, right- click a
subscription,
> and then click Properties.
> but didnt find the Subscription directory under subscription database.
> How can I configure?
> Thanks in advance.
> Naveed.
>
|||Hello Hilary!!!
Thanks for your reply, You gave solution for Pull Subscription But We are
using Push Subscription and we have very slow connection for publishing data
on subscriber, i.e why we compress snapshot file in alternate location and
now we want to configure it on subscriber.
How to do that?
Thanks,
Naveed.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eQGmKXtqEHA.3416@.TK2MSFTNGP15.phx.gbl...
> the snapshot files will be compressed in the cab format in your alternate
> snapshot folder. If you are doing a pull subscription you have the option
to
> applying the snapshot (compressed or uncompressed) from an alternate
> location by using the "Use snapshot files from the following folder
option."
> You will have to prove a path to the root of the snapshot location, ie
> \\PublisherServerName\Share\ where this will map to c:\temp or wherever
you
> place your files in. If you copy these files locally you have to copy the
> directory structure from unc on, ie if you place the files in c:\temp you
> would copy the contents of unc to c:\temp.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Naveed" <nrehman@.marsonssoft.com> wrote in message
> news:OoosGusqEHA.2732@.TK2MSFTNGP09.phx.gbl...
> subscription,
>
|||use the -AltSnapshotFolder switch on your distribution agent. make sure you
uncheck the generate snapshot in the default folder location for your
snapshot properties.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:eUFealtqEHA.376@.TK2MSFTNGP14.phx.gbl...
> Hello Hilary!!!
> Thanks for your reply, You gave solution for Pull Subscription But We are
> using Push Subscription and we have very slow connection for publishing
data[vbcol=seagreen]
> on subscriber, i.e why we compress snapshot file in alternate location and
> now we want to configure it on subscriber.
> How to do that?
> Thanks,
> Naveed.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eQGmKXtqEHA.3416@.TK2MSFTNGP15.phx.gbl...
alternate[vbcol=seagreen]
option[vbcol=seagreen]
> to
> option."
> you
the[vbcol=seagreen]
you[vbcol=seagreen]
I[vbcol=seagreen]
subscription
>
sqlsql

compensating delete on replication database!

Hi
I have Merge Publication with just one Subscriber running on SQL 2000
which has been Service packed fully.
Looking at the previous posts I did uncheck 'Enforce relationship for
replication' on the Table Relationships hoping that the deletion of
records will not happen.
But for some unknown reason the records in the FK relationship is
deleted, which is causing all sorts of problems. There are no Triggers
on the database, and I could not find a pattern for the deletion it
happens randomly.
E.G. We have a 'Contacts' and 'Addresses' Table, one contact can have
more than 1 address. But for some reason the addresses are being deleted
for the contact, i am not sure where it is happening whether in
Subscriber or Publisher, but we loose the record.
Does any one has a good solution for this?
Thanks in advance.
Regards
Laks
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Do you have any user triggers at all?
Perhaps you are experiencing the compensating commands situation :
http://support.microsoft.com/default...Product=sql2k?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)!
|||Thanks Paul for the link. But I do not have any user triggers at all?
Since the 'Enforce relationship for replication' is unchecked, I am a
bit puzzled about how this is happening.
Can I apply the hotfix (the link you have sent) to the production
server? Is it safe?
Thanks once again.
Regards
Laks
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi Paul
The Hotfix is available only in SP4 Beta and not sure when it is going
to be released. In the meantime the database is loosing the records all
the way through. Can you suggest any intermediate solutions? somethings
I need to check etc..
Thanks
Laks
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The two suggestions weren't related - user triggers was just one other
posibility.
If it is a compensation issue, you should be able to reproduce. An address
added successfully at one site will be deleted if it cannot be applied at
the other due to a PK/FK error, constraint error etc. So, you need to check
that the schemas are identical wrt these tables (SQLCompare?). If you can
find an address that repeatedly gets removed then tracking/removing the
constraint should be simple.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)!
|||Hi Paul
Thanks for the reply. There is not pattern these records are deleted and
I am not able to re-create it as well.
The Addresses Table has 2 FK relationship one to the AddressType Table
and one to the Contact Table were the records are all present. It is
only the Address records that gets deleted.
Any other areas to look into, please...
Thanks
Laks
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi Paul
I am really sorry, there is a Trigger created by another developer on
the Addresses Table, which maintaines the Ref. Intergerity. Could this
be the cause for this 'compensating deletion', if so how to overcome
this, do we need to remove the triggers?
Regards
Laks
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!