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??
Showing posts with label replication. Show all posts
Showing posts with label replication. Show all posts
Friday, March 30, 2012
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
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
netbios and named pipes sql replication.
A client that we replicate to is receiving some
netbios request that are originating from our
distribution server. I looked in the protocol
section to see which protocol is on top. I
assume the one on top is the order of which
protocol it will try to use first. Both us and
the subscriber have tcp/ip listed first.
However, they are receiving netbios request from
our machine. We have netbios over tcp/ip
disabled. Therefore, i am guessing that the
distributor is trying to use named pipes to
communicate. Is this correct? Does named pipes
even use netbios for discovery?
tia..
-comb
-comb
yes Named Pipes uses netbios.
we had a situation after apply a MS patch to the SQL server which disabled
netbios connections (security hole).
Clients (ODBC) which had been setup to use TCP/IP would switch to named
pipes if the TCP/IP connection could not be made or was dropped sometine in
the life of the ODBC. Once the client switched to named pipes, it never
switches back to TC/IP. It remains at the last protocol it made a good
connection with.
When we took named pipes support off the SQL server with the MS patch, those
clients could not connect.
We had to manually walk thru the ODBC setup and configure the CLIENT
CONFIGURATION to use the TCP/IP library.
Even if the client was using a native or 3rd party connector the client uses
the last good connection library to make all subsequent connections to that
SQL server.
It is actually stored in the registry, but the easiest way to change it is
thru an ODBC configuration.
You may have a similar issue with the distributor server acting as the
client in this case.
DS
"Combfilter" <adsf@.asdf.com> wrote in message
news:MPG.1ba7a7e4990ef73c9896a7@.news.newsreader.co m...
> A client that we replicate to is receiving some
> netbios request that are originating from our
> distribution server. I looked in the protocol
> section to see which protocol is on top. I
> assume the one on top is the order of which
> protocol it will try to use first. Both us and
> the subscriber have tcp/ip listed first.
> However, they are receiving netbios request from
> our machine. We have netbios over tcp/ip
> disabled. Therefore, i am guessing that the
> distributor is trying to use named pipes to
> communicate. Is this correct? Does named pipes
> even use netbios for discovery?
> tia..
> -comb
|||In article <10jrt6rrko7fc4e@.news.supernews.com>,
donald.stewart2@.alcoa.com says...
> -comb
> yes Named Pipes uses netbios.
> we had a situation after apply a MS patch to the SQL server which disabled
> netbios connections (security hole).
> Clients (ODBC) which had been setup to use TCP/IP would switch to named
> pipes if the TCP/IP connection could not be made or was dropped sometine in
> the life of the ODBC. Once the client switched to named pipes, it never
> switches back to TC/IP. It remains at the last protocol it made a good
> connection with.
> When we took named pipes support off the SQL server with the MS patch, those
> clients could not connect.
> We had to manually walk thru the ODBC setup and configure the CLIENT
> CONFIGURATION to use the TCP/IP library.
> Even if the client was using a native or 3rd party connector the client uses
> the last good connection library to make all subsequent connections to that
> SQL server.
> It is actually stored in the registry, but the easiest way to change it is
> thru an ODBC configuration.
> You may have a similar issue with the distributor server acting as the
> client in this case.
> DS
>
Thanks DS..
I believe this is exactally what is happening.
It's interesting to know that it defaults to the
last known good protocol. I figured it would
always try to connect with the first protocol in
the list.
I appreciate the info.
-comb
netbios request that are originating from our
distribution server. I looked in the protocol
section to see which protocol is on top. I
assume the one on top is the order of which
protocol it will try to use first. Both us and
the subscriber have tcp/ip listed first.
However, they are receiving netbios request from
our machine. We have netbios over tcp/ip
disabled. Therefore, i am guessing that the
distributor is trying to use named pipes to
communicate. Is this correct? Does named pipes
even use netbios for discovery?
tia..
-comb
-comb
yes Named Pipes uses netbios.
we had a situation after apply a MS patch to the SQL server which disabled
netbios connections (security hole).
Clients (ODBC) which had been setup to use TCP/IP would switch to named
pipes if the TCP/IP connection could not be made or was dropped sometine in
the life of the ODBC. Once the client switched to named pipes, it never
switches back to TC/IP. It remains at the last protocol it made a good
connection with.
When we took named pipes support off the SQL server with the MS patch, those
clients could not connect.
We had to manually walk thru the ODBC setup and configure the CLIENT
CONFIGURATION to use the TCP/IP library.
Even if the client was using a native or 3rd party connector the client uses
the last good connection library to make all subsequent connections to that
SQL server.
It is actually stored in the registry, but the easiest way to change it is
thru an ODBC configuration.
You may have a similar issue with the distributor server acting as the
client in this case.
DS
"Combfilter" <adsf@.asdf.com> wrote in message
news:MPG.1ba7a7e4990ef73c9896a7@.news.newsreader.co m...
> A client that we replicate to is receiving some
> netbios request that are originating from our
> distribution server. I looked in the protocol
> section to see which protocol is on top. I
> assume the one on top is the order of which
> protocol it will try to use first. Both us and
> the subscriber have tcp/ip listed first.
> However, they are receiving netbios request from
> our machine. We have netbios over tcp/ip
> disabled. Therefore, i am guessing that the
> distributor is trying to use named pipes to
> communicate. Is this correct? Does named pipes
> even use netbios for discovery?
> tia..
> -comb
|||In article <10jrt6rrko7fc4e@.news.supernews.com>,
donald.stewart2@.alcoa.com says...
> -comb
> yes Named Pipes uses netbios.
> we had a situation after apply a MS patch to the SQL server which disabled
> netbios connections (security hole).
> Clients (ODBC) which had been setup to use TCP/IP would switch to named
> pipes if the TCP/IP connection could not be made or was dropped sometine in
> the life of the ODBC. Once the client switched to named pipes, it never
> switches back to TC/IP. It remains at the last protocol it made a good
> connection with.
> When we took named pipes support off the SQL server with the MS patch, those
> clients could not connect.
> We had to manually walk thru the ODBC setup and configure the CLIENT
> CONFIGURATION to use the TCP/IP library.
> Even if the client was using a native or 3rd party connector the client uses
> the last good connection library to make all subsequent connections to that
> SQL server.
> It is actually stored in the registry, but the easiest way to change it is
> thru an ODBC configuration.
> You may have a similar issue with the distributor server acting as the
> client in this case.
> DS
>
Thanks DS..
I believe this is exactally what is happening.
It's interesting to know that it defaults to the
last known good protocol. I figured it would
always try to connect with the first protocol in
the list.
I appreciate the info.
-comb
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?
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?
Subscribe to:
Posts (Atom)