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
Showing posts with label internet. Show all posts
Showing posts with label internet. Show all posts
Monday, March 26, 2012
Monday, March 19, 2012
Merge Replication over Internet with MSDE and Sql Server (Urgent)
Hello,
I would like to setup Merge Replication between a central Sql Server as
publisher and a variety of MSDE clients as subscribers. The catch that I am
running into is that I want to be able to do this over the Internet. I have
set this up with SQL CE, so I assume that it is possible with MSDE, however,
I just can't seem to find any documentation on this. I would appreciate it
if someone could tell me if this is possible or not.
Other questions I have (but have not research a ton for yet are)
1) How can I programatically kick off a sync on the MSDE from a .NET
application?
2) If conflicts occur, how can I programatically get the conflicts back to
the client application to display in a form and allow the user to resolve
them?
It is frustrating that this is so easy with SQL CE and here I can't seem to
figure out how to do it with MSDE.
Thanks so much for your help.
Marie
Create your publication for anonymous pull. Use the merge ActiveX control on
the subscriber to pull the subscription.
You will need to specify the publisher name, network name (ie ipaddress or
FQDN), and transport mechanism using Publisher, PublisherAddress, and
PublisherNetwork properties respectively.
Check out this link for more info.
http://support.microsoft.com/default...&Product=sql2k
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Marie" <Marie@.discussions.microsoft.com> wrote in message
news:70B8068D-06BA-4036-9433-BF3B5FBB9714@.microsoft.com...
> Hello,
> I would like to setup Merge Replication between a central Sql Server as
> publisher and a variety of MSDE clients as subscribers. The catch that I
am
> running into is that I want to be able to do this over the Internet. I
have
> set this up with SQL CE, so I assume that it is possible with MSDE,
however,
> I just can't seem to find any documentation on this. I would appreciate
it
> if someone could tell me if this is possible or not.
> Other questions I have (but have not research a ton for yet are)
> 1) How can I programatically kick off a sync on the MSDE from a .NET
> application?
> 2) If conflicts occur, how can I programatically get the conflicts back to
> the client application to display in a form and allow the user to resolve
> them?
> It is frustrating that this is so easy with SQL CE and here I can't seem
to
> figure out how to do it with MSDE.
> Thanks so much for your help.
> Marie
>
>
>
|||Actually I am a little wrong on question 2. With Windows Synchronization
Manager, you click on your subscription, click on properties, click on
other, and select Resolve Conflicts Interactively.
You can also use the Microsoft SQL Conflict Resolver control for this.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23sqW9bYiEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Create your publication for anonymous pull. Use the merge ActiveX control
on
> the subscriber to pull the subscription.
> You will need to specify the publisher name, network name (ie ipaddress or
> FQDN), and transport mechanism using Publisher, PublisherAddress, and
> PublisherNetwork properties respectively.
> Check out this link for more info.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Marie" <Marie@.discussions.microsoft.com> wrote in message
> news:70B8068D-06BA-4036-9433-BF3B5FBB9714@.microsoft.com...
I[vbcol=seagreen]
> am
> have
> however,
> it
to[vbcol=seagreen]
resolve
> to
>
|||BTW - your answer to number 2 is AFAIK - no. When you set up your merge
publication for interactive conflict resolution, pull it using Windows
Synchronization Manager, and a conflict occurs you get a dialog telling you
a conflict has occured and to contact your system administrator.
At this point you can educate your users to open the Conflict Resolver on
their own, or simply to contact you and you can resolve them.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23sqW9bYiEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Create your publication for anonymous pull. Use the merge ActiveX control
on
> the subscriber to pull the subscription.
> You will need to specify the publisher name, network name (ie ipaddress or
> FQDN), and transport mechanism using Publisher, PublisherAddress, and
> PublisherNetwork properties respectively.
> Check out this link for more info.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Marie" <Marie@.discussions.microsoft.com> wrote in message
> news:70B8068D-06BA-4036-9433-BF3B5FBB9714@.microsoft.com...
I[vbcol=seagreen]
> am
> have
> however,
> it
to[vbcol=seagreen]
resolve
> to
>
I would like to setup Merge Replication between a central Sql Server as
publisher and a variety of MSDE clients as subscribers. The catch that I am
running into is that I want to be able to do this over the Internet. I have
set this up with SQL CE, so I assume that it is possible with MSDE, however,
I just can't seem to find any documentation on this. I would appreciate it
if someone could tell me if this is possible or not.
Other questions I have (but have not research a ton for yet are)
1) How can I programatically kick off a sync on the MSDE from a .NET
application?
2) If conflicts occur, how can I programatically get the conflicts back to
the client application to display in a form and allow the user to resolve
them?
It is frustrating that this is so easy with SQL CE and here I can't seem to
figure out how to do it with MSDE.
Thanks so much for your help.
Marie
Create your publication for anonymous pull. Use the merge ActiveX control on
the subscriber to pull the subscription.
You will need to specify the publisher name, network name (ie ipaddress or
FQDN), and transport mechanism using Publisher, PublisherAddress, and
PublisherNetwork properties respectively.
Check out this link for more info.
http://support.microsoft.com/default...&Product=sql2k
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Marie" <Marie@.discussions.microsoft.com> wrote in message
news:70B8068D-06BA-4036-9433-BF3B5FBB9714@.microsoft.com...
> Hello,
> I would like to setup Merge Replication between a central Sql Server as
> publisher and a variety of MSDE clients as subscribers. The catch that I
am
> running into is that I want to be able to do this over the Internet. I
have
> set this up with SQL CE, so I assume that it is possible with MSDE,
however,
> I just can't seem to find any documentation on this. I would appreciate
it
> if someone could tell me if this is possible or not.
> Other questions I have (but have not research a ton for yet are)
> 1) How can I programatically kick off a sync on the MSDE from a .NET
> application?
> 2) If conflicts occur, how can I programatically get the conflicts back to
> the client application to display in a form and allow the user to resolve
> them?
> It is frustrating that this is so easy with SQL CE and here I can't seem
to
> figure out how to do it with MSDE.
> Thanks so much for your help.
> Marie
>
>
>
|||Actually I am a little wrong on question 2. With Windows Synchronization
Manager, you click on your subscription, click on properties, click on
other, and select Resolve Conflicts Interactively.
You can also use the Microsoft SQL Conflict Resolver control for this.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23sqW9bYiEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Create your publication for anonymous pull. Use the merge ActiveX control
on
> the subscriber to pull the subscription.
> You will need to specify the publisher name, network name (ie ipaddress or
> FQDN), and transport mechanism using Publisher, PublisherAddress, and
> PublisherNetwork properties respectively.
> Check out this link for more info.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Marie" <Marie@.discussions.microsoft.com> wrote in message
> news:70B8068D-06BA-4036-9433-BF3B5FBB9714@.microsoft.com...
I[vbcol=seagreen]
> am
> have
> however,
> it
to[vbcol=seagreen]
resolve
> to
>
|||BTW - your answer to number 2 is AFAIK - no. When you set up your merge
publication for interactive conflict resolution, pull it using Windows
Synchronization Manager, and a conflict occurs you get a dialog telling you
a conflict has occured and to contact your system administrator.
At this point you can educate your users to open the Conflict Resolver on
their own, or simply to contact you and you can resolve them.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23sqW9bYiEHA.3428@.TK2MSFTNGP11.phx.gbl...
> Create your publication for anonymous pull. Use the merge ActiveX control
on
> the subscriber to pull the subscription.
> You will need to specify the publisher name, network name (ie ipaddress or
> FQDN), and transport mechanism using Publisher, PublisherAddress, and
> PublisherNetwork properties respectively.
> Check out this link for more info.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Marie" <Marie@.discussions.microsoft.com> wrote in message
> news:70B8068D-06BA-4036-9433-BF3B5FBB9714@.microsoft.com...
I[vbcol=seagreen]
> am
> have
> however,
> it
to[vbcol=seagreen]
resolve
> to
>
Merge Replication over internet Problem: Couldn't propagate schema to the subscriber.
Hello All,
I am implementing Pull merge replication over internet, I have a sql
server which I have set as Publishe/Distributor and MSDE which I have
set a subscriber. I have a sample Database FTP_REPL which I have
published. whenever I try to run merge Agent it succssfully connects
to the publisher, Distributor,but it gives error "The schema script
<ScriptName> could not be propagated to the subscriber".
Plz anyone help me to resolve this problem.
Locate your agent, right click on it, select agent properties, and ensure
the job owner is sa. Then restart your agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501100407.d4c3f56@.posting.google.co m...
> Hello All,
> I am implementing Pull merge replication over internet, I have a sql
> server which I have set as Publishe/Distributor and MSDE which I have
> set a subscriber. I have a sample Database FTP_REPL which I have
> published. whenever I try to run merge Agent it succssfully connects
> to the publisher, Distributor,but it gives error "The schema script
> <ScriptName> could not be propagated to the subscriber".
> Plz anyone help me to resolve this problem.
I am implementing Pull merge replication over internet, I have a sql
server which I have set as Publishe/Distributor and MSDE which I have
set a subscriber. I have a sample Database FTP_REPL which I have
published. whenever I try to run merge Agent it succssfully connects
to the publisher, Distributor,but it gives error "The schema script
<ScriptName> could not be propagated to the subscriber".
Plz anyone help me to resolve this problem.
Locate your agent, right click on it, select agent properties, and ensure
the job owner is sa. Then restart your agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501100407.d4c3f56@.posting.google.co m...
> Hello All,
> I am implementing Pull merge replication over internet, I have a sql
> server which I have set as Publishe/Distributor and MSDE which I have
> set a subscriber. I have a sample Database FTP_REPL which I have
> published. whenever I try to run merge Agent it succssfully connects
> to the publisher, Distributor,but it gives error "The schema script
> <ScriptName> could not be propagated to the subscriber".
> Plz anyone help me to resolve this problem.
Labels:
couldnt,
database,
distributor,
implementing,
internet,
merge,
microsoft,
msde,
mysql,
oracle,
propagate,
publishe,
pull,
replication,
schema,
server,
sql,
sqlserver,
subscriber
Merge Replication over internet Problem: Couldn't propagate schema to the subscriber.
Yesterday I posted my problem on the group I would like to explain it
a bit so that I be able to make things more clear.
1. I have set up a Sql server as publisher/Distributor.
2. Setup MSDE as subscriber
3. Login mode to publisher/subscriber/Distributor is Sql Server
Authentication
and Login Name is SUPERVISOR.
4. Setup a merge pull replication over internet, using FTP snapshot to
be
downloaded from my FTP site 61.11.103.3
5. After all this setting I ran merge agent at the subscriber site
(owner of
the agent is SUPERVISOR)using sp_start_job stored procedure.
6. Following is the list of message that I can see in Job history of
merge
agent.
A. Connecting to Subscriber.
B. Connecting to Distributor.
C. Initializing.
D. Connecting to Publisher.
E. Retrieving publication information.
F. retrieving subscription information.
G. Snapshot files will be downloaded via FTP.
H. connecting to FTP site '61'11.103.3'
I. The subscription has been marked for reinitialization,
reinitialization
will occur next time you synchronize this subscription.
J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
\FTPDB_1.sch'could not be propagated to the subscriber.
K.Process could not retrieve file
'IM19_FTP_REPL_FTPREPL\20050110104749
\FTPDB_1.sch' from FTP site 61.11.103.3
L. The schema script could not be propagated to the
subscriber,Access denied:
File not Found.
M. The job failed. The job invoked by supervisor,the last step was
step 1.
Plz help me out, Hilary has mentioned in reply to my last mail to
change owner of the merge agent to 'Sa' but this is not working out
still I m getting the same problem.
Its very urgent and important too..
Ruchir,
Based on the error message it seems ftp login doesn't have the permission to
access the snapshot folder share on your distributor box. Please make sure
that ftp login has read permission to your snapshot folder. You can verify
it by using the ftp get cmd for your ftpdb_1.sch file.
thanks - Deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501102129.51fa8110@.posting.google.c om...
> Yesterday I posted my problem on the group I would like to explain it
> a bit so that I be able to make things more clear.
> 1. I have set up a Sql server as publisher/Distributor.
> 2. Setup MSDE as subscriber
> 3. Login mode to publisher/subscriber/Distributor is Sql Server
> Authentication
> and Login Name is SUPERVISOR.
> 4. Setup a merge pull replication over internet, using FTP snapshot to
> be
> downloaded from my FTP site 61.11.103.3
> 5. After all this setting I ran merge agent at the subscriber site
> (owner of
> the agent is SUPERVISOR)using sp_start_job stored procedure.
> 6. Following is the list of message that I can see in Job history of
> merge
> agent.
> A. Connecting to Subscriber.
> B. Connecting to Distributor.
> C. Initializing.
> D. Connecting to Publisher.
> E. Retrieving publication information.
> F. retrieving subscription information.
> G. Snapshot files will be downloaded via FTP.
> H. connecting to FTP site '61'11.103.3'
> I. The subscription has been marked for reinitialization,
> reinitialization
> will occur next time you synchronize this subscription.
> J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
> Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
> \FTPDB_1.sch'could not be propagated to the subscriber.
> K.Process could not retrieve file
> 'IM19_FTP_REPL_FTPREPL\20050110104749
> \FTPDB_1.sch' from FTP site 61.11.103.3
> L. The schema script could not be propagated to the
> subscriber,Access denied:
> File not Found.
> M. The job failed. The job invoked by supervisor,the last step was
> step 1.
>
> Plz help me out, Hilary has mentioned in reply to my last mail to
> change owner of the merge agent to 'Sa' but this is not working out
> still I m getting the same problem.
> Its very urgent and important too..
a bit so that I be able to make things more clear.
1. I have set up a Sql server as publisher/Distributor.
2. Setup MSDE as subscriber
3. Login mode to publisher/subscriber/Distributor is Sql Server
Authentication
and Login Name is SUPERVISOR.
4. Setup a merge pull replication over internet, using FTP snapshot to
be
downloaded from my FTP site 61.11.103.3
5. After all this setting I ran merge agent at the subscriber site
(owner of
the agent is SUPERVISOR)using sp_start_job stored procedure.
6. Following is the list of message that I can see in Job history of
merge
agent.
A. Connecting to Subscriber.
B. Connecting to Distributor.
C. Initializing.
D. Connecting to Publisher.
E. Retrieving publication information.
F. retrieving subscription information.
G. Snapshot files will be downloaded via FTP.
H. connecting to FTP site '61'11.103.3'
I. The subscription has been marked for reinitialization,
reinitialization
will occur next time you synchronize this subscription.
J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
\FTPDB_1.sch'could not be propagated to the subscriber.
K.Process could not retrieve file
'IM19_FTP_REPL_FTPREPL\20050110104749
\FTPDB_1.sch' from FTP site 61.11.103.3
L. The schema script could not be propagated to the
subscriber,Access denied:
File not Found.
M. The job failed. The job invoked by supervisor,the last step was
step 1.
Plz help me out, Hilary has mentioned in reply to my last mail to
change owner of the merge agent to 'Sa' but this is not working out
still I m getting the same problem.
Its very urgent and important too..
Ruchir,
Based on the error message it seems ftp login doesn't have the permission to
access the snapshot folder share on your distributor box. Please make sure
that ftp login has read permission to your snapshot folder. You can verify
it by using the ftp get cmd for your ftpdb_1.sch file.
thanks - Deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501102129.51fa8110@.posting.google.c om...
> Yesterday I posted my problem on the group I would like to explain it
> a bit so that I be able to make things more clear.
> 1. I have set up a Sql server as publisher/Distributor.
> 2. Setup MSDE as subscriber
> 3. Login mode to publisher/subscriber/Distributor is Sql Server
> Authentication
> and Login Name is SUPERVISOR.
> 4. Setup a merge pull replication over internet, using FTP snapshot to
> be
> downloaded from my FTP site 61.11.103.3
> 5. After all this setting I ran merge agent at the subscriber site
> (owner of
> the agent is SUPERVISOR)using sp_start_job stored procedure.
> 6. Following is the list of message that I can see in Job history of
> merge
> agent.
> A. Connecting to Subscriber.
> B. Connecting to Distributor.
> C. Initializing.
> D. Connecting to Publisher.
> E. Retrieving publication information.
> F. retrieving subscription information.
> G. Snapshot files will be downloaded via FTP.
> H. connecting to FTP site '61'11.103.3'
> I. The subscription has been marked for reinitialization,
> reinitialization
> will occur next time you synchronize this subscription.
> J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
> Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
> \FTPDB_1.sch'could not be propagated to the subscriber.
> K.Process could not retrieve file
> 'IM19_FTP_REPL_FTPREPL\20050110104749
> \FTPDB_1.sch' from FTP site 61.11.103.3
> L. The schema script could not be propagated to the
> subscriber,Access denied:
> File not Found.
> M. The job failed. The job invoked by supervisor,the last step was
> step 1.
>
> Plz help me out, Hilary has mentioned in reply to my last mail to
> change owner of the merge agent to 'Sa' but this is not working out
> still I m getting the same problem.
> Its very urgent and important too..
Merge replication over internet
Good morning,
I am attempting to set up merge replication between a SQL Server on SBS2003
box (publisher and distributor) and a SQL Server 2000 box (subscriber) in a
different state (hosted, connect via IP addresses).
I can push the publication to the subscriber, but the synch process fails
with error 14010 (I think..not in front of right now).
This is my first attempt at replication...any help is appreciated
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||Not really. You can push or pull within a LAN, locally, or within a trusted
network or across a WAN, Internet, etc.
The decision to use push or pull depends on many factors
1) pull performance is better, but you have no central point of
administration
2) It is a security risk to open the ports necessary to push over the
internet.
3) You can't do a push using FTP.
4) pull is better when your subscribers are occasionally connected, push is
better when they are always connected.
In general when you hear the word internet - think pull.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:OEs0JSgXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> OK...so a push to the subscriber does not work? Is that only for
> local/Lan/trusted setups?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...
> the
Did[vbcol=seagreen]
DBAs.[vbcol=seagreen]
Have
> a
>
I am attempting to set up merge replication between a SQL Server on SBS2003
box (publisher and distributor) and a SQL Server 2000 box (subscriber) in a
different state (hosted, connect via IP addresses).
I can push the publication to the subscriber, but the synch process fails
with error 14010 (I think..not in front of right now).
This is my first attempt at replication...any help is appreciated
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||Not really. You can push or pull within a LAN, locally, or within a trusted
network or across a WAN, Internet, etc.
The decision to use push or pull depends on many factors
1) pull performance is better, but you have no central point of
administration
2) It is a security risk to open the ports necessary to push over the
internet.
3) You can't do a push using FTP.
4) pull is better when your subscribers are occasionally connected, push is
better when they are always connected.
In general when you hear the word internet - think pull.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:OEs0JSgXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> OK...so a push to the subscriber does not work? Is that only for
> local/Lan/trusted setups?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...
> the
Did[vbcol=seagreen]
DBAs.[vbcol=seagreen]
Have
> a
>
Labels:
attempting,
box,
database,
distributor,
internet,
merge,
microsoft,
mysql,
oracle,
publisher,
replication,
sbs2003box,
server,
sql
merge replication over internet
Hello!
I'm doing replication over non-trusted domains. I'm using FTP server to do
that.
I've also read Paul's articel about replication over non - trusted domains.
I'm using snapshot and merge replication.
Snapshot replication works OK, without any problems, but MERGE replication
gives me this error:
The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
The process could not connect to FTP site 'PC' using port 21.
(Source: STREZNIK\SAOP (Agent); Error number: 0)
------
Can you help me,
Uros
Uros,
this type of replication normally falls down due to
configuration/connectivity issues that have to be looked at individually.
Please try using an FTP tool to test transferring the snapshot files.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul!
Does MERGE replication need any different settings than snapshot. Because
snapshot over FTP works without any problems.
What are the most common settings that make troubles for MERGE via FTP?
Thanks.
"Paul Ibison" wrote:
> Uros,
> this type of replication normally falls down due to
> configuration/connectivity issues that have to be looked at individually.
> Please try using an FTP tool to test transferring the snapshot files.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Sorry to ask the obvious, but are your FTP settings done correctly on the
merge publication (inc folder paths).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Well, I've made it as for SNAPSHOT.
Here are my settings:
I have path for ftp \SAOPReplication\ftp
Just the same as for SNAPSHOT.
Should tha path be different?
"Paul Ibison" wrote:
> Sorry to ask the obvious, but are your FTP settings done correctly on the
> merge publication (inc folder paths).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Uros,
please can you post up the results of sp_helpmergepublication and
sp_helppublication for the merge and snapshot publications.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul!
Here are the results of those store procedures.
I hope you can sort this out on notepad. I've tried and it worked.
id name
description
status retention sync_mode allow_push allow_pull allow_anonymous
centralized_conflicts priority snapshot_ready
publication_type pubid snapshot_jobid
enabled_for_internet dynamic_filters has_subscription
snapshot_in_defaultfolder alt_snapshot_folder
pre_snapshot_script
post_snapshot_script
compress_snapshot ftp_address
ftp_port ftp_subdirectory
ftp_login
conflict_retention keep_partition_changes
allow_subscription_copy allow_synctoalternate validate_subscriber_info
backward_comp_level publish_to_activedirectory max_concurrent_merge
max_concurrent_dynamic_snapshots
------
-----------
-- -- -- -- -- --
-- -- --
-- --
-- -- --
-- --
-----------
-----------
-----------
------
-----------
------
-- -- --
-----------
-
-- -- --
1 MERGE_STRANKE_SAOPsf
Merge
publication of SAOPsf database from Publisher PC.
1 14 0 1 1 1
1 100.0 1 0
817F7880-1B66-4C7E-8D8D-1AD3270328B7
0x679F4FFFFA5CAE418DC4919151EBD05A 1 0 0
0 \\PC\D$\SAOP\Replikacije
NULL
NULL
1 PC
21 \SAOPreplikacije\ftp
SQLRemote
14 0 0
0 NULL
40 0
0 0
pubid name
restricted
status task replication frequency synchronization method description
immediate_sync enabled_for_internet allow_push allow_pull
allow_anonymous independent_agent immediate_sync_ready allow_sync_tran
autogen_sync_procs snapshot_jobid retention has
subscription allow_queued_tran snapshot_in_defaultfolder alt_snapshot_folder
pre_snapshot_script
post_snapshot_script
compress_snapshot ftp_address
ftp_port ftp_subdirectory
ftp_login
allow_dts
allow_subscription_copy centralized_conflicts conflict_retention
conflict_policy queue_type backward_comp_level publish_to_AD
------
-- -- -- -- --
-----------
-- -- -- -- --
-- -- -- --
-- -- --
-- --
-----------
-----------
-----------
------
-----------
------
-- -- -- --
-- -- -- --
2 SNAPSHOT_ARTIKLI_SAOPsf
0 1
1 1 0 Snapshot
publication of SAOPsf database from Publisher PC.
1 1 1 1 1
1 1 0 0
0x30961C9177CEEF4AA8EDF9FE69CC7E01 336 1 0
0 \\PC\D$\SAOP\Replikacije
NULL
NULL
1 PC
21 \SAOPReplikacije\ftp
SqlService
0 0 NULL
14 NULL NULL 10 0
|||Can the subscriber resolve the host name PC to the FTP Server? It probably
needs to be a Fully Qualified Domain Name like PC.MyDomain.Com, or you need
a hosts file entry mapping PC to the IP address of the FTP server.
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
"uros" <uros@.discussions.microsoft.com> wrote in message
news:3D947F9B-2DA3-4C75-9860-1401E33EEB3C@.microsoft.com...
> Hello!
> I'm doing replication over non-trusted domains. I'm using FTP server to do
> that.
> I've also read Paul's articel about replication over non - trusted
> domains.
> I'm using snapshot and merge replication.
> Snapshot replication works OK, without any problems, but MERGE replication
> gives me this error:
> The schema script '' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> The process could not connect to FTP site 'PC' using port 21.
> (Source: STREZNIK\SAOP (Agent); Error number: 0)
> ------
> Can you help me,
> Uros
|||Hilary!
I've done that. I've updated the host file. And as I said, SNAPSHOT
replication works fine via FTP, but merge replication fails with that error.
I don't know, how to continue and I have a deadline.
U.
"Hilary Cotter" wrote:
> Can the subscriber resolve the host name PC to the FTP Server? It probably
> needs to be a Fully Qualified Domain Name like PC.MyDomain.Com, or you need
> a hosts file entry mapping PC to the IP address of the FTP server.
> --
> 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
> "uros" <uros@.discussions.microsoft.com> wrote in message
> news:3D947F9B-2DA3-4C75-9860-1401E33EEB3C@.microsoft.com...
>
>
|||Uros,
sorry - even in notepad this is pretty difficult. Please can you set the
query analyser to output the results to text and use a Pipe delimiter, then
repost the results.
Cheers,
Paul Ibison
"uros" <uros@.discussions.microsoft.com> wrote in message
news:3D470926-AEBC-48BB-9875-F2FA879D2CA0@.microsoft.com...
> Paul!
> Here are the results of those store procedures.
> I hope you can sort this out on notepad. I've tried and it worked.
> id name
> description
>
> status retention sync_mode allow_push allow_pull
> allow_anonymous
> centralized_conflicts priority snapshot_ready
> publication_type pubid snapshot_jobid
> enabled_for_internet dynamic_filters has_subscription
> snapshot_in_defaultfolder alt_snapshot_folder
>
> pre_snapshot_script
>
> post_snapshot_script
>
> compress_snapshot ftp_address
> ftp_port ftp_subdirectory
>
> ftp_login
> conflict_retention keep_partition_changes
> allow_subscription_copy allow_synctoalternate validate_subscriber_info
>
> backward_comp_level publish_to_activedirectory max_concurrent_merge
> max_concurrent_dynamic_snapshots
> --
> ------
> ----------
--
> -- -- -- -- -- --
> -- -- --
> -- --
> -- -- --
> -- --
> ----------
--
> ----------
--
> ----------
--
> --
> ------
> --
> ----------
--
> ------
> -- -- --
> --
> ----------
--
> -- -- --
> --
> 1 MERGE_STRANKE_SAOPsf
> Merge
> publication of SAOPsf database from Publisher PC.
>
> 1 14 0 1 1 1
> 1 100.0 1 0
> 817F7880-1B66-4C7E-8D8D-1AD3270328B7
> 0x679F4FFFFA5CAE418DC4919151EBD05A 1 0 0
> 0 \\PC\D$\SAOP\Replikacije
>
> NULL
>
> NULL
>
> 1 PC
> 21 \SAOPreplikacije\ftp
>
> SQLRemote
> 14 0 0
> 0 NULL
>
> 40
> 0
> 0 0
> pubid name
> restricted
> status task replication frequency synchronization method
> description
>
> immediate_sync enabled_for_internet allow_push allow_pull
> allow_anonymous independent_agent immediate_sync_ready allow_sync_tran
> autogen_sync_procs snapshot_jobid retention has
> subscription allow_queued_tran snapshot_in_defaultfolder
> alt_snapshot_folder
>
> pre_snapshot_script
>
> post_snapshot_script
>
> compress_snapshot ftp_address
> ftp_port ftp_subdirectory
>
> ftp_login
> allow_dts
> allow_subscription_copy centralized_conflicts conflict_retention
> conflict_policy queue_type backward_comp_level publish_to_AD
> --
> ------
> -- -- -- -- --
> ----------
--
> -- -- -- -- --
> -- -- -- --
> -- -- --
> -- --
> ----------
--
> ----------
--
> ----------
--
> --
> ------
> --
> ----------
--
> ------
> -- -- -- --
> -- -- -- --
> 2 SNAPSHOT_ARTIKLI_SAOPsf
> 0
> 1
> 1 1 0 Snapshot
> publication of SAOPsf database from Publisher PC.
>
> 1 1 1 1 1
> 1 1 0 0
> 0x30961C9177CEEF4AA8EDF9FE69CC7E01 336 1 0
> 0 \\PC\D$\SAOP\Replikacije
>
> NULL
>
> NULL
>
> 1 PC
> 21 \SAOPReplikacije\ftp
>
> SqlService
> 0 0 NULL
> 14 NULL NULL 10 0
>
I'm doing replication over non-trusted domains. I'm using FTP server to do
that.
I've also read Paul's articel about replication over non - trusted domains.
I'm using snapshot and merge replication.
Snapshot replication works OK, without any problems, but MERGE replication
gives me this error:
The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
The process could not connect to FTP site 'PC' using port 21.
(Source: STREZNIK\SAOP (Agent); Error number: 0)
------
Can you help me,
Uros
Uros,
this type of replication normally falls down due to
configuration/connectivity issues that have to be looked at individually.
Please try using an FTP tool to test transferring the snapshot files.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul!
Does MERGE replication need any different settings than snapshot. Because
snapshot over FTP works without any problems.
What are the most common settings that make troubles for MERGE via FTP?
Thanks.
"Paul Ibison" wrote:
> Uros,
> this type of replication normally falls down due to
> configuration/connectivity issues that have to be looked at individually.
> Please try using an FTP tool to test transferring the snapshot files.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Sorry to ask the obvious, but are your FTP settings done correctly on the
merge publication (inc folder paths).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Well, I've made it as for SNAPSHOT.
Here are my settings:
I have path for ftp \SAOPReplication\ftp
Just the same as for SNAPSHOT.
Should tha path be different?
"Paul Ibison" wrote:
> Sorry to ask the obvious, but are your FTP settings done correctly on the
> merge publication (inc folder paths).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Uros,
please can you post up the results of sp_helpmergepublication and
sp_helppublication for the merge and snapshot publications.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul!
Here are the results of those store procedures.
I hope you can sort this out on notepad. I've tried and it worked.
id name
description
status retention sync_mode allow_push allow_pull allow_anonymous
centralized_conflicts priority snapshot_ready
publication_type pubid snapshot_jobid
enabled_for_internet dynamic_filters has_subscription
snapshot_in_defaultfolder alt_snapshot_folder
pre_snapshot_script
post_snapshot_script
compress_snapshot ftp_address
ftp_port ftp_subdirectory
ftp_login
conflict_retention keep_partition_changes
allow_subscription_copy allow_synctoalternate validate_subscriber_info
backward_comp_level publish_to_activedirectory max_concurrent_merge
max_concurrent_dynamic_snapshots
------
-----------
-- -- -- -- -- --
-- -- --
-- --
-- -- --
-- --
-----------
-----------
-----------
------
-----------
------
-- -- --
-----------
-
-- -- --
1 MERGE_STRANKE_SAOPsf
Merge
publication of SAOPsf database from Publisher PC.
1 14 0 1 1 1
1 100.0 1 0
817F7880-1B66-4C7E-8D8D-1AD3270328B7
0x679F4FFFFA5CAE418DC4919151EBD05A 1 0 0
0 \\PC\D$\SAOP\Replikacije
NULL
NULL
1 PC
21 \SAOPreplikacije\ftp
SQLRemote
14 0 0
0 NULL
40 0
0 0
pubid name
restricted
status task replication frequency synchronization method description
immediate_sync enabled_for_internet allow_push allow_pull
allow_anonymous independent_agent immediate_sync_ready allow_sync_tran
autogen_sync_procs snapshot_jobid retention has
subscription allow_queued_tran snapshot_in_defaultfolder alt_snapshot_folder
pre_snapshot_script
post_snapshot_script
compress_snapshot ftp_address
ftp_port ftp_subdirectory
ftp_login
allow_dts
allow_subscription_copy centralized_conflicts conflict_retention
conflict_policy queue_type backward_comp_level publish_to_AD
------
-- -- -- -- --
-----------
-- -- -- -- --
-- -- -- --
-- -- --
-- --
-----------
-----------
-----------
------
-----------
------
-- -- -- --
-- -- -- --
2 SNAPSHOT_ARTIKLI_SAOPsf
0 1
1 1 0 Snapshot
publication of SAOPsf database from Publisher PC.
1 1 1 1 1
1 1 0 0
0x30961C9177CEEF4AA8EDF9FE69CC7E01 336 1 0
0 \\PC\D$\SAOP\Replikacije
NULL
NULL
1 PC
21 \SAOPReplikacije\ftp
SqlService
0 0 NULL
14 NULL NULL 10 0
|||Can the subscriber resolve the host name PC to the FTP Server? It probably
needs to be a Fully Qualified Domain Name like PC.MyDomain.Com, or you need
a hosts file entry mapping PC to the IP address of the FTP server.
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
"uros" <uros@.discussions.microsoft.com> wrote in message
news:3D947F9B-2DA3-4C75-9860-1401E33EEB3C@.microsoft.com...
> Hello!
> I'm doing replication over non-trusted domains. I'm using FTP server to do
> that.
> I've also read Paul's articel about replication over non - trusted
> domains.
> I'm using snapshot and merge replication.
> Snapshot replication works OK, without any problems, but MERGE replication
> gives me this error:
> The schema script '' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> The process could not connect to FTP site 'PC' using port 21.
> (Source: STREZNIK\SAOP (Agent); Error number: 0)
> ------
> Can you help me,
> Uros
|||Hilary!
I've done that. I've updated the host file. And as I said, SNAPSHOT
replication works fine via FTP, but merge replication fails with that error.
I don't know, how to continue and I have a deadline.
U.
"Hilary Cotter" wrote:
> Can the subscriber resolve the host name PC to the FTP Server? It probably
> needs to be a Fully Qualified Domain Name like PC.MyDomain.Com, or you need
> a hosts file entry mapping PC to the IP address of the FTP server.
> --
> 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
> "uros" <uros@.discussions.microsoft.com> wrote in message
> news:3D947F9B-2DA3-4C75-9860-1401E33EEB3C@.microsoft.com...
>
>
|||Uros,
sorry - even in notepad this is pretty difficult. Please can you set the
query analyser to output the results to text and use a Pipe delimiter, then
repost the results.
Cheers,
Paul Ibison
"uros" <uros@.discussions.microsoft.com> wrote in message
news:3D470926-AEBC-48BB-9875-F2FA879D2CA0@.microsoft.com...
> Paul!
> Here are the results of those store procedures.
> I hope you can sort this out on notepad. I've tried and it worked.
> id name
> description
>
> status retention sync_mode allow_push allow_pull
> allow_anonymous
> centralized_conflicts priority snapshot_ready
> publication_type pubid snapshot_jobid
> enabled_for_internet dynamic_filters has_subscription
> snapshot_in_defaultfolder alt_snapshot_folder
>
> pre_snapshot_script
>
> post_snapshot_script
>
> compress_snapshot ftp_address
> ftp_port ftp_subdirectory
>
> ftp_login
> conflict_retention keep_partition_changes
> allow_subscription_copy allow_synctoalternate validate_subscriber_info
>
> backward_comp_level publish_to_activedirectory max_concurrent_merge
> max_concurrent_dynamic_snapshots
> --
> ------
> ----------
--
> -- -- -- -- -- --
> -- -- --
> -- --
> -- -- --
> -- --
> ----------
--
> ----------
--
> ----------
--
> --
> ------
> --
> ----------
--
> ------
> -- -- --
> --
> ----------
--
> -- -- --
> --
> 1 MERGE_STRANKE_SAOPsf
> Merge
> publication of SAOPsf database from Publisher PC.
>
> 1 14 0 1 1 1
> 1 100.0 1 0
> 817F7880-1B66-4C7E-8D8D-1AD3270328B7
> 0x679F4FFFFA5CAE418DC4919151EBD05A 1 0 0
> 0 \\PC\D$\SAOP\Replikacije
>
> NULL
>
> NULL
>
> 1 PC
> 21 \SAOPreplikacije\ftp
>
> SQLRemote
> 14 0 0
> 0 NULL
>
> 40
> 0
> 0 0
> pubid name
> restricted
> status task replication frequency synchronization method
> description
>
> immediate_sync enabled_for_internet allow_push allow_pull
> allow_anonymous independent_agent immediate_sync_ready allow_sync_tran
> autogen_sync_procs snapshot_jobid retention has
> subscription allow_queued_tran snapshot_in_defaultfolder
> alt_snapshot_folder
>
> pre_snapshot_script
>
> post_snapshot_script
>
> compress_snapshot ftp_address
> ftp_port ftp_subdirectory
>
> ftp_login
> allow_dts
> allow_subscription_copy centralized_conflicts conflict_retention
> conflict_policy queue_type backward_comp_level publish_to_AD
> --
> ------
> -- -- -- -- --
> ----------
--
> -- -- -- -- --
> -- -- -- --
> -- -- --
> -- --
> ----------
--
> ----------
--
> ----------
--
> --
> ------
> --
> ----------
--
> ------
> -- -- -- --
> -- -- -- --
> 2 SNAPSHOT_ARTIKLI_SAOPsf
> 0
> 1
> 1 1 0 Snapshot
> publication of SAOPsf database from Publisher PC.
>
> 1 1 1 1 1
> 1 1 0 0
> 0x30961C9177CEEF4AA8EDF9FE69CC7E01 336 1 0
> 0 \\PC\D$\SAOP\Replikacije
>
> NULL
>
> NULL
>
> 1 PC
> 21 \SAOPReplikacije\ftp
>
> SqlService
> 0 0 NULL
> 14 NULL NULL 10 0
>
Merge replication Over Internet
Have a look in the articles section of
www.replicationanswers.com - I have a posted up an
article there on just this topic.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul
Thanks for such a wonderful article, Actually I am facing a problem, you could see it as I have posted it on the group.
Actulally some days before I was implementing merge replication over internet, during that time I didn't even provide the netbios name of the remote MSDE server on the subscriber MSDE server and it worked fine.
but now on a new set of MSDE servers even if I enter all the information as you said I could not even connect to the remote server using osql facility.
Pls Pls Pls help me out I have already spent 3 days on this problem and getting frustated with each passing moment.
Originally posted by Paul Ibison
Have a look in the articles section of
www.replicationanswers.com - I have a posted up an
article there on just this topic.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html) |||Hi Paul
One more query if you could solve my doubt.
Actually while impletmenting replication over internet, I am planning to use dynamic filtering, Since we don't want to provide FTP information to over subscribers (which are obviously at distributed locations).
So I am asked to make sure that Snapshot is applied manually at the sbuscribers side, Since I am not having very much idea about how to Create Dynamic snapshot and apply it manually, Plz guide me?
Is it that If I apply snapshot manually I'll not need to specify all FTP related stuff??
Originally posted by rdhar
Hi Paul
Thanks for such a wonderful article, Actually I am facing a problem, you could see it as I have posted it on the group.
Actulally some days before I was implementing merge replication over internet, during that time I didn't even provide the netbios name of the remote MSDE server on the subscriber MSDE server and it worked fine.
but now on a new set of MSDE servers even if I enter all the information as you said I could not even connect to the remote server using osql facility.
Pls Pls Pls help me out I have already spent 3 days on this problem and getting frustated with each passing moment.
|||For a manual snapshot, you don't need the FTP settings to initialize,
however, any additional articles added to the publication will cause
problems.
I can't setthis up today, but if you're having problems with manual
application of dynamic snapshots, then yo could disable the dynamic snapshot
bit and have the filters applied to the whole snapshot. It ends up the same,
but will take longer.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Can you ping the remote server or probably ping is disabled so can you
telnet it using port 1433? IE is it 'visible' at all through firewalls.
Can you connect using the IP address in OSQL? If so, have you created the
client network alias?
Are you using a VPN? Is it FTP or fileshare initialization? Question for
initialization configuration.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
www.replicationanswers.com - I have a posted up an
article there on just this topic.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul
Thanks for such a wonderful article, Actually I am facing a problem, you could see it as I have posted it on the group.
Actulally some days before I was implementing merge replication over internet, during that time I didn't even provide the netbios name of the remote MSDE server on the subscriber MSDE server and it worked fine.
but now on a new set of MSDE servers even if I enter all the information as you said I could not even connect to the remote server using osql facility.
Pls Pls Pls help me out I have already spent 3 days on this problem and getting frustated with each passing moment.
Quote:
Have a look in the articles section of
www.replicationanswers.com - I have a posted up an
article there on just this topic.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
One more query if you could solve my doubt.
Actually while impletmenting replication over internet, I am planning to use dynamic filtering, Since we don't want to provide FTP information to over subscribers (which are obviously at distributed locations).
So I am asked to make sure that Snapshot is applied manually at the sbuscribers side, Since I am not having very much idea about how to Create Dynamic snapshot and apply it manually, Plz guide me?
Is it that If I apply snapshot manually I'll not need to specify all FTP related stuff??
Quote:
Hi Paul
Thanks for such a wonderful article, Actually I am facing a problem, you could see it as I have posted it on the group.
Actulally some days before I was implementing merge replication over internet, during that time I didn't even provide the netbios name of the remote MSDE server on the subscriber MSDE server and it worked fine.
but now on a new set of MSDE servers even if I enter all the information as you said I could not even connect to the remote server using osql facility.
Pls Pls Pls help me out I have already spent 3 days on this problem and getting frustated with each passing moment.
however, any additional articles added to the publication will cause
problems.
I can't setthis up today, but if you're having problems with manual
application of dynamic snapshots, then yo could disable the dynamic snapshot
bit and have the filters applied to the whole snapshot. It ends up the same,
but will take longer.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Can you ping the remote server or probably ping is disabled so can you
telnet it using port 1433? IE is it 'visible' at all through firewalls.
Can you connect using the IP address in OSQL? If so, have you created the
client network alias?
Are you using a VPN? Is it FTP or fileshare initialization? Question for
initialization configuration.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Merge replication on MSDE over internet
Hi,
We are having a dedicated machine (with a fix IP) running SQl2000 and it is
supposed to be the master database. And we are having 4 clients XP machine
running MSDE (without fix IP), and we would like to have a merge replication
to sync. data from / to the client / server. Coz data will be updated on
server or clients side. I have simulated this environment on a LAN
environment and it works but I 'm not sure whether if those clients machine
are connected to the server through internet via ADSL connection(without a
fix IP).
please help ... !!! thanks.
-Wing
you must use the replication ActiveX merge control. Set the
DistributorAddress and the PublisherAddress to be the IP address of your
publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
"Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it
> is
> supposed to be the master database. And we are having 4 clients XP
> machine
> running MSDE (without fix IP), and we would like to have a merge
> replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients
> machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
|||thanks... is there any sample source code on that ? besides using ActiveX
merge control, is there any way not using control ?
also does the ActiveX merge control support VB6, thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> bl
news:%23f8Kxk1yEHA.2540@.TK2MSFTNGP09.phx.gbl g...[vbcol=seagreen]
> you must use the replication ActiveX merge control. Set the
> DistributorAddress and the PublisherAddress to be the IP address of your
> publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
>
> "Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
> news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
on[vbcol=seagreen]
a
>
|||We currently have 4 locations replicating such. What I do is setup SQL Server
to dial VPN setup at our main office (Publisher). Each subscriber dials VPN,
performs replication, and then disconnects the VPN. This works great...they
sync every hour.
"Wing Chan" wrote:
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it is
> supposed to be the master database. And we are having 4 clients XP machine
> running MSDE (without fix IP), and we would like to have a merge replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
>
|||Hi
> Each subscriber dials VPN,
> performs replication, and then disconnects the VPN.
Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
job or something else?
I'll appreciate any details.
Regards,
|||Yes, just add new steps to the Merge Agent job. First step would be of Type
"Operating System Command (CmdExec)" and would read something like
rasdial vpn_connection_name user password domain:/your_domain_name
Then add another step after the Replication agent to disconnect. Same as
above but the command text would be:
rasdial vpn_connection_name /disconnect
Important Note: It appears that the Merge Agent job step attempts to run
immediately after the first Connect VPN step is run. If you're relying on
NETBIOS name resolution, you WILL need to add a retry on the replication
step. This is simply because it takes a little bit of time for your VPN IP
settings to be configured upon first connection. The first merge attempt
almost always fails for me because it can't locate the Publisher name yet. If
you're connecting via straight IP addresses, then this will not be a problem.
Besides that, this works like a charm for our multi-city office replication
on an hourly basis.
"Carlos Gutierrez" wrote:
> Hi
>
> Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
> job or something else?
> I'll appreciate any details.
> Regards,
>
>
We are having a dedicated machine (with a fix IP) running SQl2000 and it is
supposed to be the master database. And we are having 4 clients XP machine
running MSDE (without fix IP), and we would like to have a merge replication
to sync. data from / to the client / server. Coz data will be updated on
server or clients side. I have simulated this environment on a LAN
environment and it works but I 'm not sure whether if those clients machine
are connected to the server through internet via ADSL connection(without a
fix IP).
please help ... !!! thanks.
-Wing
you must use the replication ActiveX merge control. Set the
DistributorAddress and the PublisherAddress to be the IP address of your
publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
"Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it
> is
> supposed to be the master database. And we are having 4 clients XP
> machine
> running MSDE (without fix IP), and we would like to have a merge
> replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients
> machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
|||thanks... is there any sample source code on that ? besides using ActiveX
merge control, is there any way not using control ?
also does the ActiveX merge control support VB6, thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> bl
news:%23f8Kxk1yEHA.2540@.TK2MSFTNGP09.phx.gbl g...[vbcol=seagreen]
> you must use the replication ActiveX merge control. Set the
> DistributorAddress and the PublisherAddress to be the IP address of your
> publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
>
> "Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
> news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
on[vbcol=seagreen]
a
>
|||We currently have 4 locations replicating such. What I do is setup SQL Server
to dial VPN setup at our main office (Publisher). Each subscriber dials VPN,
performs replication, and then disconnects the VPN. This works great...they
sync every hour.
"Wing Chan" wrote:
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it is
> supposed to be the master database. And we are having 4 clients XP machine
> running MSDE (without fix IP), and we would like to have a merge replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
>
|||Hi
> Each subscriber dials VPN,
> performs replication, and then disconnects the VPN.
Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
job or something else?
I'll appreciate any details.
Regards,
|||Yes, just add new steps to the Merge Agent job. First step would be of Type
"Operating System Command (CmdExec)" and would read something like
rasdial vpn_connection_name user password domain:/your_domain_name
Then add another step after the Replication agent to disconnect. Same as
above but the command text would be:
rasdial vpn_connection_name /disconnect
Important Note: It appears that the Merge Agent job step attempts to run
immediately after the first Connect VPN step is run. If you're relying on
NETBIOS name resolution, you WILL need to add a retry on the replication
step. This is simply because it takes a little bit of time for your VPN IP
settings to be configured upon first connection. The first merge attempt
almost always fails for me because it can't locate the Publisher name yet. If
you're connecting via straight IP addresses, then this will not be a problem.
Besides that, this works like a charm for our multi-city office replication
on an hourly basis.
"Carlos Gutierrez" wrote:
> Hi
>
> Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
> job or something else?
> I'll appreciate any details.
> Regards,
>
>
Merge replication on MSDE over internet
Hi,
We are having a dedicated machine (with a fix IP) running SQl2000 and it is
supposed to be the master database. And we are having 4 clients XP machine
running MSDE (without fix IP), and we would like to have a merge replication
to sync. data from / to the client / server. Coz data will be updated on
server or clients side. I have simulated this environment on a LAN
environment and it works but I 'm not sure whether if those clients machine
are connected to the server through internet via ADSL connection(without a
fix IP).
please help ... !!! thanks.
-Wing
you must use the replication ActiveX merge control. Set the
DistributorAddress and the PublisherAddress to be the IP address of your
publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
"Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it
> is
> supposed to be the master database. And we are having 4 clients XP
> machine
> running MSDE (without fix IP), and we would like to have a merge
> replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients
> machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
|||thanks... is there any sample source code on that ? besides using ActiveX
merge control, is there any way not using control ?
also does the ActiveX merge control support VB6, thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> bl
news:%23f8Kxk1yEHA.2540@.TK2MSFTNGP09.phx.gbl g...[vbcol=seagreen]
> you must use the replication ActiveX merge control. Set the
> DistributorAddress and the PublisherAddress to be the IP address of your
> publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
>
> "Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
> news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
on[vbcol=seagreen]
a
>
|||We currently have 4 locations replicating such. What I do is setup SQL Server
to dial VPN setup at our main office (Publisher). Each subscriber dials VPN,
performs replication, and then disconnects the VPN. This works great...they
sync every hour.
"Wing Chan" wrote:
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it is
> supposed to be the master database. And we are having 4 clients XP machine
> running MSDE (without fix IP), and we would like to have a merge replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
>
|||Hi
> Each subscriber dials VPN,
> performs replication, and then disconnects the VPN.
Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
job or something else?
I'll appreciate any details.
Regards,
|||Yes, just add new steps to the Merge Agent job. First step would be of Type
"Operating System Command (CmdExec)" and would read something like
rasdial vpn_connection_name user password domain:/your_domain_name
Then add another step after the Replication agent to disconnect. Same as
above but the command text would be:
rasdial vpn_connection_name /disconnect
Important Note: It appears that the Merge Agent job step attempts to run
immediately after the first Connect VPN step is run. If you're relying on
NETBIOS name resolution, you WILL need to add a retry on the replication
step. This is simply because it takes a little bit of time for your VPN IP
settings to be configured upon first connection. The first merge attempt
almost always fails for me because it can't locate the Publisher name yet. If
you're connecting via straight IP addresses, then this will not be a problem.
Besides that, this works like a charm for our multi-city office replication
on an hourly basis.
"Carlos Gutierrez" wrote:
> Hi
>
> Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
> job or something else?
> I'll appreciate any details.
> Regards,
>
>
We are having a dedicated machine (with a fix IP) running SQl2000 and it is
supposed to be the master database. And we are having 4 clients XP machine
running MSDE (without fix IP), and we would like to have a merge replication
to sync. data from / to the client / server. Coz data will be updated on
server or clients side. I have simulated this environment on a LAN
environment and it works but I 'm not sure whether if those clients machine
are connected to the server through internet via ADSL connection(without a
fix IP).
please help ... !!! thanks.
-Wing
you must use the replication ActiveX merge control. Set the
DistributorAddress and the PublisherAddress to be the IP address of your
publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
"Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it
> is
> supposed to be the master database. And we are having 4 clients XP
> machine
> running MSDE (without fix IP), and we would like to have a merge
> replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients
> machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
|||thanks... is there any sample source code on that ? besides using ActiveX
merge control, is there any way not using control ?
also does the ActiveX merge control support VB6, thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> bl
news:%23f8Kxk1yEHA.2540@.TK2MSFTNGP09.phx.gbl g...[vbcol=seagreen]
> you must use the replication ActiveX merge control. Set the
> DistributorAddress and the PublisherAddress to be the IP address of your
> publisher and the DIstributorNetwork and PublisherNetwork to be TCPIP
>
> "Wing Chan" <wing_650473hk@.yahoo.com.hk> wrote in message
> news:uGjl5RxyEHA.824@.TK2MSFTNGP11.phx.gbl...
on[vbcol=seagreen]
a
>
|||We currently have 4 locations replicating such. What I do is setup SQL Server
to dial VPN setup at our main office (Publisher). Each subscriber dials VPN,
performs replication, and then disconnects the VPN. This works great...they
sync every hour.
"Wing Chan" wrote:
> Hi,
> We are having a dedicated machine (with a fix IP) running SQl2000 and it is
> supposed to be the master database. And we are having 4 clients XP machine
> running MSDE (without fix IP), and we would like to have a merge replication
> to sync. data from / to the client / server. Coz data will be updated on
> server or clients side. I have simulated this environment on a LAN
> environment and it works but I 'm not sure whether if those clients machine
> are connected to the server through internet via ADSL connection(without a
> fix IP).
> please help ... !!! thanks.
> -Wing
>
>
|||Hi
> Each subscriber dials VPN,
> performs replication, and then disconnects the VPN.
Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
job or something else?
I'll appreciate any details.
Regards,
|||Yes, just add new steps to the Merge Agent job. First step would be of Type
"Operating System Command (CmdExec)" and would read something like
rasdial vpn_connection_name user password domain:/your_domain_name
Then add another step after the Replication agent to disconnect. Same as
above but the command text would be:
rasdial vpn_connection_name /disconnect
Important Note: It appears that the Merge Agent job step attempts to run
immediately after the first Connect VPN step is run. If you're relying on
NETBIOS name resolution, you WILL need to add a retry on the replication
step. This is simply because it takes a little bit of time for your VPN IP
settings to be configured upon first connection. The first merge attempt
almost always fails for me because it can't locate the Publisher name yet. If
you're connecting via straight IP addresses, then this will not be a problem.
Besides that, this works like a charm for our multi-city office replication
on an hourly basis.
"Carlos Gutierrez" wrote:
> Hi
>
> Where do you handle the VPN dial/disconnect? Do you add a step to the Agent
> job or something else?
> I'll appreciate any details.
> Regards,
>
>
Merge replication on internet
How can we achive a SQL server merge replication over the internet when both the client and server are Windows Xp machines and using SQL Server 7? Can someone please explain in a clear step by step fashion?
Is this a static IP or not.
Basically what you have to do it configure the publisher and subscriber using client network utilty, in the alias tab. Use the current TCP/IP address and a plain text server name (ie, don't use the ip address as the alias).
Then in your hosts file ( found in cd %windir%\system32\etc edit the hosts file to include both these servernames and the ip addresses. If the addresses are dynamic you will have to modify this each time you get a new ip address.
Then you have to configure an ftp server on your publisher and configure your merge publication for ftp.
Then create a pull subscription using ftp on your subscriber.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Rammy" wrote:
> How can we achive a SQL server merge replication over the internet when both the client and server are Windows Xp machines and using SQL Server 7? Can someone please explain in a clear step by step fashion?
>
|||One more thing. When you configure your subscriber, do not use the impersonate the SQL Server Agent on the publisher, use SQL Server authentication.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" wrote:
[vbcol=seagreen]
> Is this a static IP or not.
> Basically what you have to do it configure the publisher and subscriber using client network utilty, in the alias tab. Use the current TCP/IP address and a plain text server name (ie, don't use the ip address as the alias).
> Then in your hosts file ( found in cd %windir%\system32\etc edit the hosts file to include both these servernames and the ip addresses. If the addresses are dynamic you will have to modify this each time you get a new ip address.
> Then you have to configure an ftp server on your publisher and configure your merge publication for ftp.
> Then create a pull subscription using ftp on your subscriber.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "Rammy" wrote:
Is this a static IP or not.
Basically what you have to do it configure the publisher and subscriber using client network utilty, in the alias tab. Use the current TCP/IP address and a plain text server name (ie, don't use the ip address as the alias).
Then in your hosts file ( found in cd %windir%\system32\etc edit the hosts file to include both these servernames and the ip addresses. If the addresses are dynamic you will have to modify this each time you get a new ip address.
Then you have to configure an ftp server on your publisher and configure your merge publication for ftp.
Then create a pull subscription using ftp on your subscriber.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Rammy" wrote:
> How can we achive a SQL server merge replication over the internet when both the client and server are Windows Xp machines and using SQL Server 7? Can someone please explain in a clear step by step fashion?
>
|||One more thing. When you configure your subscriber, do not use the impersonate the SQL Server Agent on the publisher, use SQL Server authentication.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" wrote:
[vbcol=seagreen]
> Is this a static IP or not.
> Basically what you have to do it configure the publisher and subscriber using client network utilty, in the alias tab. Use the current TCP/IP address and a plain text server name (ie, don't use the ip address as the alias).
> Then in your hosts file ( found in cd %windir%\system32\etc edit the hosts file to include both these servernames and the ip addresses. If the addresses are dynamic you will have to modify this each time you get a new ip address.
> Then you have to configure an ftp server on your publisher and configure your merge publication for ftp.
> Then create a pull subscription using ftp on your subscriber.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "Rammy" wrote:
Monday, March 12, 2012
Merge replication in 'SQL Server'
Hi,
I read Paul Ibison's article about "Replication Across Non-Trusted Domains
or Using the Internet".
Me (and my company) need to take a very tough decision whether using SQL
server 2005 merge replication or building our own synchronization engine.
Our big problems are:
1. Everything has to work over the internet (over port 443 only), even port
21 for ftp is not an issue…
2. Out product is for customers overseas without the ability to go through
an integration process at the client site. It means we must use some
automatic process configuring the publisher or subscriber and users running
processes, etc.
3. The installation must work from an installation cd (both client and
server), without the need to manually configure domain users to run certain
replication agents – it must also be automatically.
Which one (or all) of the demands above is possible?
We are willing to make small changes –only after we definitely know that we
must open port 21 for example.
I understood that the implementation of offline clients (doesn't matter if
it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge
replication in the SQL Server is good in theory but difficult to manage and
requires a lot of extra handling issues like opening ports and adding users
granted to run the processes for the replication process.
Are there any improvements in 2005 in these issues (I know about the option
to replicate through iis so the port problem is now solved?!).
My most important request is that I'll be glad if anybody knows and can
write about products in the open market which used this architecture.
Thanks,
Gil.
I'm in a crucial
Is it true? Are there any improvements in 2005 in these issues (I know about
the option to replicate through iis so the port problem is now solved?!).
I'll be glad if anybody knows and can write about products in the open
market which used this architecture.
Thanks,
Gil.
1) no problem, you can configure sql server to run on any port - have a
look at http://support.microsoft.com/default...b;en-us;823938 in
the section marked. However, port 443 is for https, did you want your SQL
Server traffic encrypted?
Configuring an instance of SQL Server to use a static port
2) you can script out replication jobs by right clicking on a publication
and selecting - generate sql script. You can generate the scripts necessary
to enable replication by right clicking on the replication folder and
selecting Generate SQL Scripts, and then selecting Distributor properties.
3) you can configure autorun.inf to run an executable which will run the
scripts generated above
Everything you list is possible - you suddenly start talking about SQL CE -
if your clients are running SQL CE, you will need a web server to
synchronize with. You could run over port 443 for this. I would not
characterize "Merge replication in the SQL Server is good in theory but
difficult to manage and requires a lot of extra handling issues like opening
ports and adding users granted to run the processes for the replication
process."
This is simply not true. Merge replication or any form of replication only
needs port 1433 (or whatever port you run SQL Server on) open. If you are
deploying your snapshot over the internet you will probably want port 21
open as well. Regarding the addition of users, this could be valid. You can
run pull agents on the subscribers which will connect to the publisher under
different accounts if you are doing filtering by suser_name(). But by
default you probably would not have to do this. I normally use pass through
authentication which uses the same account names.
There are lots of improvements, fixes, and features in SQL 2005. Web
synchronization is one of them. Although the documentation talks about
running over port 1433 (https) in addition to 80(http), I believe this is a
mistake.
I worked on a replication topology with over 60 merge clients. We had our
share of problems, but in general it was highly stable.
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
"Gil" <Gil@.discussions.microsoft.com> wrote in message
news:123D2E11-371E-419E-8B5F-D4710F95A008@.microsoft.com...
> Hi,
> I read Paul Ibison's article about "Replication Across Non-Trusted Domains
> or Using the Internet".
> Me (and my company) need to take a very tough decision whether using SQL
> server 2005 merge replication or building our own synchronization engine.
> Our big problems are:
> 1. Everything has to work over the internet (over port 443 only), even
port
> 21 for ftp is not an issue.
> 2. Out product is for customers overseas without the ability to go through
> an integration process at the client site. It means we must use some
> automatic process configuring the publisher or subscriber and users
running
> processes, etc.
> 3. The installation must work from an installation cd (both client and
> server), without the need to manually configure domain users to run
certain
> replication agents - it must also be automatically.
> Which one (or all) of the demands above is possible?
> We are willing to make small changes -only after we definitely know that
we
> must open port 21 for example.
> I understood that the implementation of offline clients (doesn't matter if
> it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge
> replication in the SQL Server is good in theory but difficult to manage
and
> requires a lot of extra handling issues like opening ports and adding
users
> granted to run the processes for the replication process.
> Are there any improvements in 2005 in these issues (I know about the
option
> to replicate through iis so the port problem is now solved?!).
> My most important request is that I'll be glad if anybody knows and can
> write about products in the open market which used this architecture.
> Thanks,
> Gil.
>
> I'm in a crucial
> Is it true? Are there any improvements in 2005 in these issues (I know
about
> the option to replicate through iis so the port problem is now solved?!).
> I'll be glad if anybody knows and can write about products in the open
> market which used this architecture.
> Thanks,
> Gil.
>
>
|||Thank you for your answer...
But I guess I wasn't completely clear.
We plan to use merge replication with new web replication feature available
in "SQL server 2005", and I wanted to know whether there is an option to work
with SSL over http without the need for opening the ftp port?
We definitely cannot open port 1433 because the replication will go over the
internet – and Windows authentication is not possible too.
There is also a need to use SUSER_SNAME() function in order filter by the
connected user. Is there a workaround of doing it without giving special
permissions to the user? I noticed there are security problems impersonating
the users just like that, these are the most annoying parts
Thanks,
Gil.
"Hilary Cotter" wrote:
> 1) no problem, you can configure sql server to run on any port - have a
> look at http://support.microsoft.com/default...b;en-us;823938 in
> the section marked. However, port 443 is for https, did you want your SQL
> Server traffic encrypted?
> Configuring an instance of SQL Server to use a static port
> 2) you can script out replication jobs by right clicking on a publication
> and selecting - generate sql script. You can generate the scripts necessary
> to enable replication by right clicking on the replication folder and
> selecting Generate SQL Scripts, and then selecting Distributor properties.
> 3) you can configure autorun.inf to run an executable which will run the
> scripts generated above
> Everything you list is possible - you suddenly start talking about SQL CE -
> if your clients are running SQL CE, you will need a web server to
> synchronize with. You could run over port 443 for this. I would not
> characterize "Merge replication in the SQL Server is good in theory but
> difficult to manage and requires a lot of extra handling issues like opening
> ports and adding users granted to run the processes for the replication
> process."
> This is simply not true. Merge replication or any form of replication only
> needs port 1433 (or whatever port you run SQL Server on) open. If you are
> deploying your snapshot over the internet you will probably want port 21
> open as well. Regarding the addition of users, this could be valid. You can
> run pull agents on the subscribers which will connect to the publisher under
> different accounts if you are doing filtering by suser_name(). But by
> default you probably would not have to do this. I normally use pass through
> authentication which uses the same account names.
> There are lots of improvements, fixes, and features in SQL 2005. Web
> synchronization is one of them. Although the documentation talks about
> running over port 1433 (https) in addition to 80(http), I believe this is a
> mistake.
> I worked on a replication topology with over 60 merge clients. We had our
> share of problems, but in general it was highly stable.
> --
> 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
> "Gil" <Gil@.discussions.microsoft.com> wrote in message
> news:123D2E11-371E-419E-8B5F-D4710F95A008@.microsoft.com...
> port
> running
> certain
> we
> and
> users
> option
> about
>
>
|||Re the port issue - I asked this question on the Beta newsgroup - for Merge
over the internet in SQL 2005, is HTTP (80) supported or must it be HTTPS
(443) and the reply was HTTPS only. (which makes it a pain fully testing the
whole process on XP which doesn't support certificate server). At the time I
noticed that the advice in BOL for the initial Beta2 version had some typos
and mixed the 2 - HTTP and HTTPS, or was at best misleading. I haven't
checked the new BOL yet on this issue.
Cheers,
Paul Ibison
|||Hi,
Can someone give me some real-world example of a product (not an IT project
- where a DBA be in the integration process, a product for customers
overseas) which is using web merge replication (over http only) ?
Doesn't matter if the Client is windows XP or mobile.
Thanks,
Gil.
"Paul Ibison" wrote:
> Re the port issue - I asked this question on the Beta newsgroup - for Merge
> over the internet in SQL 2005, is HTTP (80) supported or must it be HTTPS
> (443) and the reply was HTTPS only. (which makes it a pain fully testing the
> whole process on XP which doesn't support certificate server). At the time I
> noticed that the advice in BOL for the initial Beta2 version had some typos
> and mixed the 2 - HTTP and HTTPS, or was at best misleading. I haven't
> checked the new BOL yet on this issue.
> Cheers,
> Paul Ibison
>
>
|||Gil,
I'd also be interested to hear of any such products but I think we'll be
lucky - SQL Server's only in Beta2 at this stage
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I read Paul Ibison's article about "Replication Across Non-Trusted Domains
or Using the Internet".
Me (and my company) need to take a very tough decision whether using SQL
server 2005 merge replication or building our own synchronization engine.
Our big problems are:
1. Everything has to work over the internet (over port 443 only), even port
21 for ftp is not an issue…
2. Out product is for customers overseas without the ability to go through
an integration process at the client site. It means we must use some
automatic process configuring the publisher or subscriber and users running
processes, etc.
3. The installation must work from an installation cd (both client and
server), without the need to manually configure domain users to run certain
replication agents – it must also be automatically.
Which one (or all) of the demands above is possible?
We are willing to make small changes –only after we definitely know that we
must open port 21 for example.
I understood that the implementation of offline clients (doesn't matter if
it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge
replication in the SQL Server is good in theory but difficult to manage and
requires a lot of extra handling issues like opening ports and adding users
granted to run the processes for the replication process.
Are there any improvements in 2005 in these issues (I know about the option
to replicate through iis so the port problem is now solved?!).
My most important request is that I'll be glad if anybody knows and can
write about products in the open market which used this architecture.
Thanks,
Gil.
I'm in a crucial
Is it true? Are there any improvements in 2005 in these issues (I know about
the option to replicate through iis so the port problem is now solved?!).
I'll be glad if anybody knows and can write about products in the open
market which used this architecture.
Thanks,
Gil.
1) no problem, you can configure sql server to run on any port - have a
look at http://support.microsoft.com/default...b;en-us;823938 in
the section marked. However, port 443 is for https, did you want your SQL
Server traffic encrypted?
Configuring an instance of SQL Server to use a static port
2) you can script out replication jobs by right clicking on a publication
and selecting - generate sql script. You can generate the scripts necessary
to enable replication by right clicking on the replication folder and
selecting Generate SQL Scripts, and then selecting Distributor properties.
3) you can configure autorun.inf to run an executable which will run the
scripts generated above
Everything you list is possible - you suddenly start talking about SQL CE -
if your clients are running SQL CE, you will need a web server to
synchronize with. You could run over port 443 for this. I would not
characterize "Merge replication in the SQL Server is good in theory but
difficult to manage and requires a lot of extra handling issues like opening
ports and adding users granted to run the processes for the replication
process."
This is simply not true. Merge replication or any form of replication only
needs port 1433 (or whatever port you run SQL Server on) open. If you are
deploying your snapshot over the internet you will probably want port 21
open as well. Regarding the addition of users, this could be valid. You can
run pull agents on the subscribers which will connect to the publisher under
different accounts if you are doing filtering by suser_name(). But by
default you probably would not have to do this. I normally use pass through
authentication which uses the same account names.
There are lots of improvements, fixes, and features in SQL 2005. Web
synchronization is one of them. Although the documentation talks about
running over port 1433 (https) in addition to 80(http), I believe this is a
mistake.
I worked on a replication topology with over 60 merge clients. We had our
share of problems, but in general it was highly stable.
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
"Gil" <Gil@.discussions.microsoft.com> wrote in message
news:123D2E11-371E-419E-8B5F-D4710F95A008@.microsoft.com...
> Hi,
> I read Paul Ibison's article about "Replication Across Non-Trusted Domains
> or Using the Internet".
> Me (and my company) need to take a very tough decision whether using SQL
> server 2005 merge replication or building our own synchronization engine.
> Our big problems are:
> 1. Everything has to work over the internet (over port 443 only), even
port
> 21 for ftp is not an issue.
> 2. Out product is for customers overseas without the ability to go through
> an integration process at the client site. It means we must use some
> automatic process configuring the publisher or subscriber and users
running
> processes, etc.
> 3. The installation must work from an installation cd (both client and
> server), without the need to manually configure domain users to run
certain
> replication agents - it must also be automatically.
> Which one (or all) of the demands above is possible?
> We are willing to make small changes -only after we definitely know that
we
> must open port 21 for example.
> I understood that the implementation of offline clients (doesn't matter if
> it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge
> replication in the SQL Server is good in theory but difficult to manage
and
> requires a lot of extra handling issues like opening ports and adding
users
> granted to run the processes for the replication process.
> Are there any improvements in 2005 in these issues (I know about the
option
> to replicate through iis so the port problem is now solved?!).
> My most important request is that I'll be glad if anybody knows and can
> write about products in the open market which used this architecture.
> Thanks,
> Gil.
>
> I'm in a crucial
> Is it true? Are there any improvements in 2005 in these issues (I know
about
> the option to replicate through iis so the port problem is now solved?!).
> I'll be glad if anybody knows and can write about products in the open
> market which used this architecture.
> Thanks,
> Gil.
>
>
|||Thank you for your answer...
But I guess I wasn't completely clear.
We plan to use merge replication with new web replication feature available
in "SQL server 2005", and I wanted to know whether there is an option to work
with SSL over http without the need for opening the ftp port?
We definitely cannot open port 1433 because the replication will go over the
internet – and Windows authentication is not possible too.
There is also a need to use SUSER_SNAME() function in order filter by the
connected user. Is there a workaround of doing it without giving special
permissions to the user? I noticed there are security problems impersonating
the users just like that, these are the most annoying parts
Thanks,
Gil.
"Hilary Cotter" wrote:
> 1) no problem, you can configure sql server to run on any port - have a
> look at http://support.microsoft.com/default...b;en-us;823938 in
> the section marked. However, port 443 is for https, did you want your SQL
> Server traffic encrypted?
> Configuring an instance of SQL Server to use a static port
> 2) you can script out replication jobs by right clicking on a publication
> and selecting - generate sql script. You can generate the scripts necessary
> to enable replication by right clicking on the replication folder and
> selecting Generate SQL Scripts, and then selecting Distributor properties.
> 3) you can configure autorun.inf to run an executable which will run the
> scripts generated above
> Everything you list is possible - you suddenly start talking about SQL CE -
> if your clients are running SQL CE, you will need a web server to
> synchronize with. You could run over port 443 for this. I would not
> characterize "Merge replication in the SQL Server is good in theory but
> difficult to manage and requires a lot of extra handling issues like opening
> ports and adding users granted to run the processes for the replication
> process."
> This is simply not true. Merge replication or any form of replication only
> needs port 1433 (or whatever port you run SQL Server on) open. If you are
> deploying your snapshot over the internet you will probably want port 21
> open as well. Regarding the addition of users, this could be valid. You can
> run pull agents on the subscribers which will connect to the publisher under
> different accounts if you are doing filtering by suser_name(). But by
> default you probably would not have to do this. I normally use pass through
> authentication which uses the same account names.
> There are lots of improvements, fixes, and features in SQL 2005. Web
> synchronization is one of them. Although the documentation talks about
> running over port 1433 (https) in addition to 80(http), I believe this is a
> mistake.
> I worked on a replication topology with over 60 merge clients. We had our
> share of problems, but in general it was highly stable.
> --
> 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
> "Gil" <Gil@.discussions.microsoft.com> wrote in message
> news:123D2E11-371E-419E-8B5F-D4710F95A008@.microsoft.com...
> port
> running
> certain
> we
> and
> users
> option
> about
>
>
|||Re the port issue - I asked this question on the Beta newsgroup - for Merge
over the internet in SQL 2005, is HTTP (80) supported or must it be HTTPS
(443) and the reply was HTTPS only. (which makes it a pain fully testing the
whole process on XP which doesn't support certificate server). At the time I
noticed that the advice in BOL for the initial Beta2 version had some typos
and mixed the 2 - HTTP and HTTPS, or was at best misleading. I haven't
checked the new BOL yet on this issue.
Cheers,
Paul Ibison
|||Hi,
Can someone give me some real-world example of a product (not an IT project
- where a DBA be in the integration process, a product for customers
overseas) which is using web merge replication (over http only) ?
Doesn't matter if the Client is windows XP or mobile.
Thanks,
Gil.
"Paul Ibison" wrote:
> Re the port issue - I asked this question on the Beta newsgroup - for Merge
> over the internet in SQL 2005, is HTTP (80) supported or must it be HTTPS
> (443) and the reply was HTTPS only. (which makes it a pain fully testing the
> whole process on XP which doesn't support certificate server). At the time I
> noticed that the advice in BOL for the initial Beta2 version had some typos
> and mixed the 2 - HTTP and HTTPS, or was at best misleading. I haven't
> checked the new BOL yet on this issue.
> Cheers,
> Paul Ibison
>
>
|||Gil,
I'd also be interested to hear of any such products but I think we'll be
lucky - SQL Server's only in Beta2 at this stage
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Saturday, February 25, 2012
Merge Replication between two servers not connected via internet and on two separate domains
I have two sql server 2000 databases and I wish to do merge replication between them, the problem is that they are not connected via the internet (no ping) and are on two separate domains in different countries.
I can use email and I can use encrypted ftp.
I am wondering if I could use sql ce merge replication to a pocket pc which creates an sdf file, that I then email backwards and forwards and build identical publication and subscriptions at either server to merge sync with this sdf file through a pocket pc.
Has anyone done this before?
Does anyone have any other suggestions?
It's not going to be possible. Merge replication is built with partners that can publish/subscribe to each other. If all you have is email/ftp, you will have to roll your own "merge" - take look at bcp/bulkload/dts in book online.Monday, February 20, 2012
Merge Replication across the internet
Hi,
I require to replicate data 2 ways across the internet.
I think merge replication would be the best way to do this.
How secure is it across the internet ?
Is there anyway to create a file out of differences to be applied to
another database.
I am using SQL Server 2000
Srini,
yes this is possible with a few treaks.
To make it completely secure, most people use a VPN.
File-based replication is not possible.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I require to replicate data 2 ways across the internet.
I think merge replication would be the best way to do this.
How secure is it across the internet ?
Is there anyway to create a file out of differences to be applied to
another database.
I am using SQL Server 2000
Srini,
yes this is possible with a few treaks.
To make it completely secure, most people use a VPN.
File-based replication is not possible.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
merge Replication across Internet
I'm want to setup merge replication ( sql 2000 ) where one sql server would
be installed with a hosting provider & other would be in our office. I'm
able to setup a test setup in my office between 2 servers which are in same
NT domain.
I have queries about how to setting up merge replication over internet. I
request all sql replication expertes to please answer my query.
1. While setting up merge replication is it a must to have point to point
connect i.e do we need to have a leased line connectivity between hosting
provider where we would be hosting sql server & our office ?
2. The server hosted in hosting provider should be made to log in to our NT
office domain or can i keep this server in standalone mode & achieve merge
replication ?
2.My office has internet connectivity via some isp. If leased line
connectivity to hosting provider is not possible then how can i setup merge
replication on internet ? At my server hosted in hosting provider do i need
to setup vpn ( l2tp ) connectivity to my server in office ? Please note that
in my test setup in office both servers were in same NT domain & connected in
a LAN.Idea of vpn connectivity is to extend my office network over internet
to the server hosted in hosting provider. is my direction of thinking right ?
Please share your experiences if some one in this forumn has implmented a
similar setup.
tanks.....
1) You need some form of connectivity - whether it is across the internet or
through a dedicated lease line doesn't matter. You might want to use a VPN
for security requirements.
2) You don't need to create a trust relationship between your domain and the
hosting company server/domain. You would use SQL authentication and FTP for
this. Consult this kb for more information.
http://support.microsoft.com/default...b;en-us;321822
2) As long as you can connect to both servers using Enterprise Manager you
will be ok. Note that you will probably want to register both servers using
the NetBIOS names (what is returned via select @.@.servername and which should
match xp_cmdshell 'hostname'). Use Client Network Utility to build an alias
which will match the Fully Qualified DomainName of the SQL Server i.e.
(SQLServer1.ResourceDomain.Microsoft.com).
Using a VPN is not essential. Microsoft does recommend it for security
reasons. If you are concerned about security (i.e. are a bank or have
sensitive data) use a VPN, if you are not concerned you don't have to use a
VPN. Using a VPN slows down communication, because of this many companies
choose not to use it.
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
"PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
news:470A0759-D7D8-4275-BDB1-58F4B4BCC3B2@.microsoft.com...
> I'm want to setup merge replication ( sql 2000 ) where one sql server
would
> be installed with a hosting provider & other would be in our office. I'm
> able to setup a test setup in my office between 2 servers which are in
same
> NT domain.
> I have queries about how to setting up merge replication over internet. I
> request all sql replication expertes to please answer my query.
> 1. While setting up merge replication is it a must to have point to point
> connect i.e do we need to have a leased line connectivity between hosting
> provider where we would be hosting sql server & our office ?
> 2. The server hosted in hosting provider should be made to log in to our
NT
> office domain or can i keep this server in standalone mode & achieve
merge
> replication ?
> 2.My office has internet connectivity via some isp. If leased line
> connectivity to hosting provider is not possible then how can i setup
merge
> replication on internet ? At my server hosted in hosting provider do i
need
> to setup vpn ( l2tp ) connectivity to my server in office ? Please note
that
> in my test setup in office both servers were in same NT domain & connected
in
> a LAN.Idea of vpn connectivity is to extend my office network over
internet
> to the server hosted in hosting provider. is my direction of thinking
right ?
> Please share your experiences if some one in this forumn has implmented a
> similar setup.
> tanks.....
>
|||Many thanks for reply.I suppose my office network has firewall & suppose
hosting provider also has firewall, then for merge replication which ports
would be involved?Based on your inputs will talk to my network team in office
regarding the same.
"Hilary Cotter" wrote:
> 1) You need some form of connectivity - whether it is across the internet or
> through a dedicated lease line doesn't matter. You might want to use a VPN
> for security requirements.
> 2) You don't need to create a trust relationship between your domain and the
> hosting company server/domain. You would use SQL authentication and FTP for
> this. Consult this kb for more information.
> http://support.microsoft.com/default...b;en-us;321822
> 2) As long as you can connect to both servers using Enterprise Manager you
> will be ok. Note that you will probably want to register both servers using
> the NetBIOS names (what is returned via select @.@.servername and which should
> match xp_cmdshell 'hostname'). Use Client Network Utility to build an alias
> which will match the Fully Qualified DomainName of the SQL Server i.e.
> (SQLServer1.ResourceDomain.Microsoft.com).
> Using a VPN is not essential. Microsoft does recommend it for security
> reasons. If you are concerned about security (i.e. are a bank or have
> sensitive data) use a VPN, if you are not concerned you don't have to use a
> VPN. Using a VPN slows down communication, because of this many companies
> choose not to use it.
> --
> 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
> "PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
> news:470A0759-D7D8-4275-BDB1-58F4B4BCC3B2@.microsoft.com...
> would
> same
> NT
> merge
> merge
> need
> that
> in
> internet
> right ?
>
>
|||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
"PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
news:1A422957-611D-45FC-8D3E-A734340ECC27@.microsoft.com...
> Many thanks for reply.I suppose my office network has firewall & suppose
> hosting provider also has firewall, then for merge replication which ports
> would be involved?Based on your inputs will talk to my network team in
office[vbcol=seagreen]
> regarding the same.
> "Hilary Cotter" wrote:
internet or[vbcol=seagreen]
VPN[vbcol=seagreen]
the[vbcol=seagreen]
for[vbcol=seagreen]
you[vbcol=seagreen]
using[vbcol=seagreen]
should[vbcol=seagreen]
alias[vbcol=seagreen]
use a[vbcol=seagreen]
companies[vbcol=seagreen]
I'm[vbcol=seagreen]
internet. I[vbcol=seagreen]
point[vbcol=seagreen]
hosting[vbcol=seagreen]
our[vbcol=seagreen]
note[vbcol=seagreen]
connected[vbcol=seagreen]
implmented a[vbcol=seagreen]
|||ports 1433 and 21 (for ftp).
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
"PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
news:1A422957-611D-45FC-8D3E-A734340ECC27@.microsoft.com...
> Many thanks for reply.I suppose my office network has firewall & suppose
> hosting provider also has firewall, then for merge replication which ports
> would be involved?Based on your inputs will talk to my network team in
office[vbcol=seagreen]
> regarding the same.
> "Hilary Cotter" wrote:
internet or[vbcol=seagreen]
VPN[vbcol=seagreen]
the[vbcol=seagreen]
for[vbcol=seagreen]
you[vbcol=seagreen]
using[vbcol=seagreen]
should[vbcol=seagreen]
alias[vbcol=seagreen]
use a[vbcol=seagreen]
companies[vbcol=seagreen]
I'm[vbcol=seagreen]
internet. I[vbcol=seagreen]
point[vbcol=seagreen]
hosting[vbcol=seagreen]
our[vbcol=seagreen]
note[vbcol=seagreen]
connected[vbcol=seagreen]
implmented a[vbcol=seagreen]
be installed with a hosting provider & other would be in our office. I'm
able to setup a test setup in my office between 2 servers which are in same
NT domain.
I have queries about how to setting up merge replication over internet. I
request all sql replication expertes to please answer my query.
1. While setting up merge replication is it a must to have point to point
connect i.e do we need to have a leased line connectivity between hosting
provider where we would be hosting sql server & our office ?
2. The server hosted in hosting provider should be made to log in to our NT
office domain or can i keep this server in standalone mode & achieve merge
replication ?
2.My office has internet connectivity via some isp. If leased line
connectivity to hosting provider is not possible then how can i setup merge
replication on internet ? At my server hosted in hosting provider do i need
to setup vpn ( l2tp ) connectivity to my server in office ? Please note that
in my test setup in office both servers were in same NT domain & connected in
a LAN.Idea of vpn connectivity is to extend my office network over internet
to the server hosted in hosting provider. is my direction of thinking right ?
Please share your experiences if some one in this forumn has implmented a
similar setup.
tanks.....
1) You need some form of connectivity - whether it is across the internet or
through a dedicated lease line doesn't matter. You might want to use a VPN
for security requirements.
2) You don't need to create a trust relationship between your domain and the
hosting company server/domain. You would use SQL authentication and FTP for
this. Consult this kb for more information.
http://support.microsoft.com/default...b;en-us;321822
2) As long as you can connect to both servers using Enterprise Manager you
will be ok. Note that you will probably want to register both servers using
the NetBIOS names (what is returned via select @.@.servername and which should
match xp_cmdshell 'hostname'). Use Client Network Utility to build an alias
which will match the Fully Qualified DomainName of the SQL Server i.e.
(SQLServer1.ResourceDomain.Microsoft.com).
Using a VPN is not essential. Microsoft does recommend it for security
reasons. If you are concerned about security (i.e. are a bank or have
sensitive data) use a VPN, if you are not concerned you don't have to use a
VPN. Using a VPN slows down communication, because of this many companies
choose not to use it.
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
"PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
news:470A0759-D7D8-4275-BDB1-58F4B4BCC3B2@.microsoft.com...
> I'm want to setup merge replication ( sql 2000 ) where one sql server
would
> be installed with a hosting provider & other would be in our office. I'm
> able to setup a test setup in my office between 2 servers which are in
same
> NT domain.
> I have queries about how to setting up merge replication over internet. I
> request all sql replication expertes to please answer my query.
> 1. While setting up merge replication is it a must to have point to point
> connect i.e do we need to have a leased line connectivity between hosting
> provider where we would be hosting sql server & our office ?
> 2. The server hosted in hosting provider should be made to log in to our
NT
> office domain or can i keep this server in standalone mode & achieve
merge
> replication ?
> 2.My office has internet connectivity via some isp. If leased line
> connectivity to hosting provider is not possible then how can i setup
merge
> replication on internet ? At my server hosted in hosting provider do i
need
> to setup vpn ( l2tp ) connectivity to my server in office ? Please note
that
> in my test setup in office both servers were in same NT domain & connected
in
> a LAN.Idea of vpn connectivity is to extend my office network over
internet
> to the server hosted in hosting provider. is my direction of thinking
right ?
> Please share your experiences if some one in this forumn has implmented a
> similar setup.
> tanks.....
>
|||Many thanks for reply.I suppose my office network has firewall & suppose
hosting provider also has firewall, then for merge replication which ports
would be involved?Based on your inputs will talk to my network team in office
regarding the same.
"Hilary Cotter" wrote:
> 1) You need some form of connectivity - whether it is across the internet or
> through a dedicated lease line doesn't matter. You might want to use a VPN
> for security requirements.
> 2) You don't need to create a trust relationship between your domain and the
> hosting company server/domain. You would use SQL authentication and FTP for
> this. Consult this kb for more information.
> http://support.microsoft.com/default...b;en-us;321822
> 2) As long as you can connect to both servers using Enterprise Manager you
> will be ok. Note that you will probably want to register both servers using
> the NetBIOS names (what is returned via select @.@.servername and which should
> match xp_cmdshell 'hostname'). Use Client Network Utility to build an alias
> which will match the Fully Qualified DomainName of the SQL Server i.e.
> (SQLServer1.ResourceDomain.Microsoft.com).
> Using a VPN is not essential. Microsoft does recommend it for security
> reasons. If you are concerned about security (i.e. are a bank or have
> sensitive data) use a VPN, if you are not concerned you don't have to use a
> VPN. Using a VPN slows down communication, because of this many companies
> choose not to use it.
> --
> 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
> "PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
> news:470A0759-D7D8-4275-BDB1-58F4B4BCC3B2@.microsoft.com...
> would
> same
> NT
> merge
> merge
> need
> that
> in
> internet
> right ?
>
>
|||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
"PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
news:1A422957-611D-45FC-8D3E-A734340ECC27@.microsoft.com...
> Many thanks for reply.I suppose my office network has firewall & suppose
> hosting provider also has firewall, then for merge replication which ports
> would be involved?Based on your inputs will talk to my network team in
office[vbcol=seagreen]
> regarding the same.
> "Hilary Cotter" wrote:
internet or[vbcol=seagreen]
VPN[vbcol=seagreen]
the[vbcol=seagreen]
for[vbcol=seagreen]
you[vbcol=seagreen]
using[vbcol=seagreen]
should[vbcol=seagreen]
alias[vbcol=seagreen]
use a[vbcol=seagreen]
companies[vbcol=seagreen]
I'm[vbcol=seagreen]
internet. I[vbcol=seagreen]
point[vbcol=seagreen]
hosting[vbcol=seagreen]
our[vbcol=seagreen]
note[vbcol=seagreen]
connected[vbcol=seagreen]
implmented a[vbcol=seagreen]
|||ports 1433 and 21 (for ftp).
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
"PELEAANIL" <PELEAANIL@.discussions.microsoft.com> wrote in message
news:1A422957-611D-45FC-8D3E-A734340ECC27@.microsoft.com...
> Many thanks for reply.I suppose my office network has firewall & suppose
> hosting provider also has firewall, then for merge replication which ports
> would be involved?Based on your inputs will talk to my network team in
office[vbcol=seagreen]
> regarding the same.
> "Hilary Cotter" wrote:
internet or[vbcol=seagreen]
VPN[vbcol=seagreen]
the[vbcol=seagreen]
for[vbcol=seagreen]
you[vbcol=seagreen]
using[vbcol=seagreen]
should[vbcol=seagreen]
alias[vbcol=seagreen]
use a[vbcol=seagreen]
companies[vbcol=seagreen]
I'm[vbcol=seagreen]
internet. I[vbcol=seagreen]
point[vbcol=seagreen]
hosting[vbcol=seagreen]
our[vbcol=seagreen]
note[vbcol=seagreen]
connected[vbcol=seagreen]
implmented a[vbcol=seagreen]
Subscribe to:
Posts (Atom)