Showing posts with label subscriber. Show all posts
Showing posts with label subscriber. Show all posts

Friday, March 30, 2012

Network Connectivity between Distributor & Subscriber - Replication

What happens when Network Connectivity between Distributor & Subscriber
fails in Transactional Replication ??
Thanks,
JohnFix the network connectivity and restart the subscriber.|||Thank You. What happens to the transactions between Publisher/distributor/subscriber when Network failure??

Monday, March 26, 2012

netbios and sql replication

If i have netbios enabled on the distributor is there any way to make it
not request netbios information to the subscriber? I have the
subscriber in the host file and in the client network utility. That
should halt nebios request, but it doesn't. The subscriber keeps seeing
netbios request coming from our distributor?
Would adding the subscriber to the lmhost help more then adding it to
the host?
thanks,
comb
probably not. Hostname resolution goes through a hierarchy trying to resolve
the hostname, sometimes Netbios cache, WINS server first, broadcast,
lmhosts, hosts, DNS, sometimes DNS (if the host name has a . in it) first.
It depends on a variety of settings.
Why is this important to you. Once the server knows about a name it caches
it and doesn't do the lookup again.
"combfilter" <asdf@.adsf.com> wrote in message
news:MPG.1cc9e0a2c18ba491989680@.news.newsreader.co m...
> If i have netbios enabled on the distributor is there any way to make it
> not request netbios information to the subscriber? I have the
> subscriber in the host file and in the client network utility. That
> should halt nebios request, but it doesn't. The subscriber keeps seeing
> netbios request coming from our distributor?
> Would adding the subscriber to the lmhost help more then adding it to
> the host?
> thanks,
> comb
|||Our subscriber is complaining about netbios request from our distributor
in their firewall logs.
The subscriber is in the host file so our machine shouldn't even need to
do a netbios request. However, for some reason it is. Also, the host
file does work. I can make changes to it and they take place
immediatly.
Mostly I just want to stop it to make the subscriber happy.
In article <#nf51xfQFHA.3704@.TK2MSFTNGP12.phx.gbl>,
hilary.cotter@.gmail.com says...
> probably not. Hostname resolution goes through a hierarchy trying to resolve
> the hostname, sometimes Netbios cache, WINS server first, broadcast,
> lmhosts, hosts, DNS, sometimes DNS (if the host name has a . in it) first.
> It depends on a variety of settings.
> Why is this important to you. Once the server knows about a name it caches
> it and doesn't do the lookup again.
> "combfilter" <asdf@.adsf.com> wrote in message
> news:MPG.1cc9e0a2c18ba491989680@.news.newsreader.co m...
>
>
sql

Monday, February 20, 2012

Need to trigger a script to run after merge replication finishes

After a subscriber connects to the network and merges the data with the
publisher I’m looking for a way to trigger a script to run. Is there
anything built into SQL Server to do such a thing?
Normally this is done with a final job step. Right click on your merge
agent, select agent properties, click on steps, and add a 4th job. Have the
3rd steps On Failure action be quit with failure, and on Success action be
go to next step.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pauly C" <paulysc@.optonline.net> wrote in message
news:8E4CE71B-F2D0-432E-8FD5-887E7805174B@.microsoft.com...
> After a subscriber connects to the network and merges the data with the
> publisher I'm looking for a way to trigger a script to run. Is there
> anything built into SQL Server to do such a thing?