What’s the best way to secure merge replication over the internet? The cl
ient is running MSDE and could be a home user with broadband. If it’s usi
ng a VPN would this be SSL or IPSec?Either would secure the traffic from MSDE to the Publisher.
VPN would allow the client to use other corporate resources as well and
authenticate using Windows
Authentication.
At a minimum put a server certificates on the Publisher and update the
Trusted Root Authority
on the Subscriber (MSDE) and use SSL.
316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft
http://support.microsoft.com/?id=316898
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
If you have an ISA Server, you could publish the SQL resource as well.
Here's some docs on using ISA.
http://www.microsoft.com/technet/pr...tain/proxy.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin - I left out some important details. Actually, the client side
would be the Publisher (MSDE). We would like to use replication to backup
the database with our application for our customers.
"Kevin McDonnell [MSFT]" wrote:
> Either would secure the traffic from MSDE to the Publisher.
> VPN would allow the client to use other corporate resources as well and
> authenticate using Windows
> Authentication.
> At a minimum put a server certificates on the Publisher and update the
> Trusted Root Authority
> on the Subscriber (MSDE) and use SSL.
> 316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft
> http://support.microsoft.com/?id=316898
> 276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
> Server
> http://support.microsoft.com/?id=276553
> If you have an ISA Server, you could publish the SQL resource as well.
> Here's some docs on using ISA.
> http://www.microsoft.com/technet/pr...tain/proxy.mspx
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Thanks Kevin - I left out some important details. Actually, the client side
(MSDE) would be the publisher. We would like to use replication to backup
the databases with our application for our customers.
"Kevin McDonnell [MSFT]" wrote:
> Either would secure the traffic from MSDE to the Publisher.
> VPN would allow the client to use other corporate resources as well and
> authenticate using Windows
> Authentication.
> At a minimum put a server certificates on the Publisher and update the
> Trusted Root Authority
> on the Subscriber (MSDE) and use SSL.
> 316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft
> http://support.microsoft.com/?id=316898
> 276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
> Server
> http://support.microsoft.com/?id=276553
> If you have an ISA Server, you could publish the SQL resource as well.
> Here's some docs on using ISA.
> http://www.microsoft.com/technet/pr...tain/proxy.mspx
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||OK. Then the MSDE machine (Publisher) would require the server certificate
then.
Also, SQL Replication is not really a backup strategy... Many customers use
Transactional Replication
to provide a warm standby for their Published database, but you should also
have a good backup strategy in place in case there
are hardware failures, that require complete recovery.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
I'm working on a similar situation (trying to implement SSL between 2
MSSQL 2000 boxes for replication).
Is there any way to implement the envryption (SSL) for the connections
used during the replication, other than the "force encryption" options
in the client and/or server network utility?
TIA.
Mike
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Hi Mike,
In SQL 2000 we use protocol encryption to enable SSL. If you are using
Default instances of SQL for Replication you can also use the older network
library called MultiProtocol.
164667 INF: Replication Setup Over a Firewall
http://support.microsoft.com/?id=164667
Other options are: IPSec between the two machines or a VPN connection
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Showing posts with label internet. Show all posts
Showing posts with label internet. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
Replication Problem
We have same database at our Head office and at factory. we use merge replication over internet to synchronize both databases.
The problem is that the internet connection is not good and keep on breaking. Is there some other way to replicate database.Originally posted by saleem
We have same database at our Head office and at factory. we use merge replication over internet to synchronize both databases.
The problem is that the internet connection is not good and keep on breaking. Is there some other way to replicate database.
Have a look at Agent profiles, for the merge agent. Perhaps change the profile to a "Slow Link Agent Profile."
Tim|||Dear colleague
You can solve (partially) the problem by augmenting the timeout factor in the merge-agent.
Simply open SQL manager, and look into the database you need, under the folder replication manager, and go to the Agents folder. Open the Merge agents subfolder and look for the one which replicates the table(s) you need.
Right click on the merge agent of your choice and select properties.
Go to the Tab Steps and select the step Run Agent. click on Edit and you'll see the merge instruction appear. At the end of this instruction you can insert a timeout factor: -QueryTimeOut 120 (120 seconds).
Save the edited entry and try it out. Try also several timeout factors ( in seconds) for optimal performance.
I hope this helps you!
Greetings,
Vincent
Originally posted by saleem
We have same database at our Head office and at factory. we use merge replication over internet to synchronize both databases.
The problem is that the internet connection is not good and keep on breaking. Is there some other way to replicate database.
The problem is that the internet connection is not good and keep on breaking. Is there some other way to replicate database.Originally posted by saleem
We have same database at our Head office and at factory. we use merge replication over internet to synchronize both databases.
The problem is that the internet connection is not good and keep on breaking. Is there some other way to replicate database.
Have a look at Agent profiles, for the merge agent. Perhaps change the profile to a "Slow Link Agent Profile."
Tim|||Dear colleague
You can solve (partially) the problem by augmenting the timeout factor in the merge-agent.
Simply open SQL manager, and look into the database you need, under the folder replication manager, and go to the Agents folder. Open the Merge agents subfolder and look for the one which replicates the table(s) you need.
Right click on the merge agent of your choice and select properties.
Go to the Tab Steps and select the step Run Agent. click on Edit and you'll see the merge instruction appear. At the end of this instruction you can insert a timeout factor: -QueryTimeOut 120 (120 seconds).
Save the edited entry and try it out. Try also several timeout factors ( in seconds) for optimal performance.
I hope this helps you!
Greetings,
Vincent
Originally posted by saleem
We have same database at our Head office and at factory. we use merge replication over internet to synchronize both databases.
The problem is that the internet connection is not good and keep on breaking. Is there some other way to replicate database.
Tuesday, March 20, 2012
replication please help
Hi gurus, plz help me out!
SNAPSHOT! :mad:
Publisher: 1.5 GB of size. Push merge subscription.256 K full duplex internet connection.
Subscriber: physically at different country. T1 connection. I dial VPN to connect to the publisher which is in seperate domain. Since the domains are different, i am using SQL authentication for my replication process.
The problem with the snapshot is "disconnectivity". Merge agent starts form beginning after running for 2 or 3 hours. I have following entries for MSrepl_errors table in the distribution database:
error_code -2147201001 "The process could not deliver the snapshot to the Subscriber"
error_code 20037 "The process could not bulk copy into table '"dbo"."MY_TABLE"'"
error_code 11 "General network error. Check your network documentation."
The thing that bothers me much is that the VPN scarcely disconnects, only a single packet drop forces the merge agent to retry!!!. To isolate the problem i started ping reqest from publisher to subscriber; i saw merge agent to fail when a packet loss occured for only one second. VPN did not disconnect.
Currently i've chosen "slow link" profile for merge agent.
I started the snapshot 2 days ago and it restarts after every 2 or 3 hours.
Why the heck merge agent starts from the beginning; couldn't it be handled to start where it was when the connection was lost? Packet-loss is normal on the internet connections. I would love to know how u people replicate VLDBs over the internet.
I tried dynamic snapshot but found it rather risky; the merge agent stops with success during the middle of snapshot if connection is dropped leaving the subscriber with inconsistent data.
Any ideas and tips would be very much appreciated.
Howdy!I need u Guys!! :(|||An awful lot depends on what got lost, and where it got lost in the process. Merge replication is also a hodge-podge kind of thing, it is usually "interesting" trying to figure out where the "beginning" of it is, since it scarcely differentiates the difference between tables, much less any order to their changes.
Connections are definitely not "parts is parts" around the world. A connection from one part of the US to another is frequently "rock solid". A connection from here to London is very nearly as good, as is one from London to Sydney. One from the United States to Sydney is absolutely awful. So, we move the data going to Sydney through London... Even though it ends up going most of the way around the world instead of only about one fourth of the way, it is still ots more reliable.
Unless you have lots of time, energy, and money, this is where I'd bring in the "hired guns" to solve the problem. If you bring in someone like Microsoft Professional Services that deals with the various IP providers, knows the problems that exist between point A and point B, and understands the way that your specific replication setup is configured, you'll get an answer much faster and in the long run cheaper than trying to find the solution yourself.
-PatP|||Hi, Pat. Thanx for ur feedback.
I've tried this thing.
Publisher name SERVER1
Subscriber name SERVER2
I uploaded the SNAPSHOT.CAB (300 MB) from the publisher using download manager (if connection disconnects, it resumes where the connection was lost). It got uploaded in 3 hours.
Now i dropped the push merge subscription. Created Pull merge subscription at SERVER2. Placed the SNAPSHOT.CAB into local C drive of SERVER2.
The location i've extracted the snapshot file is:
C:\unc\SERVER1_MBDB_MBDB_PUBLICATION\2004061923325 2
In the Snapshot Location dialogbox for pull merge agent, I specified this location to force the agent to pick snapshot locally.
When i run the merge agent; it fails, for it searches the snapshot files from the default location at the publisher rather than the one i specified :mad: . The error is:
The schema script '\\SERVER1\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SERVER1_MBDB_MBDB_PUBLIC ATION\20040619233252\UR_TABLE_1.sch' could not be propagated to the subscriber.
Could not find the cabinet file 'snapshot.cab' in folder 'c:\unc\SERVER1_MBDB_MBDB_PUBLICATION\200406192332 52\unc\SERVER1_MBDB_MBDB_PUBLICATION\2004061923325 2\'
How can i square this location problem.
Any Help!!
Thanx for bearing along!|||If you are using a Merge PULL subscription, check the subscription properties at the subscriber to be sure that they specify the correct directory.
I'm a bit nervous about making suggestions, since you are making some pretty significant changes to what you are doing (push versus pull, where the agent exectutes, etc). Be careful to think out what you are doing!
-PatP|||Hi, thanx again 4 ur reply.
I did specify the correct directory where i placed the snapshot files. But the merge agent tries to access the snapshot from publisher's default directory rather than the local path.
I am tryin to use pull instead of push, for push won't work in my case due to disconnection. However i could move the whole snapshot.cab file to subscriber using a download manager despite the connection is lost b/w the transfer. But it isn't working either here. :confused:
SNAPSHOT! :mad:
Publisher: 1.5 GB of size. Push merge subscription.256 K full duplex internet connection.
Subscriber: physically at different country. T1 connection. I dial VPN to connect to the publisher which is in seperate domain. Since the domains are different, i am using SQL authentication for my replication process.
The problem with the snapshot is "disconnectivity". Merge agent starts form beginning after running for 2 or 3 hours. I have following entries for MSrepl_errors table in the distribution database:
error_code -2147201001 "The process could not deliver the snapshot to the Subscriber"
error_code 20037 "The process could not bulk copy into table '"dbo"."MY_TABLE"'"
error_code 11 "General network error. Check your network documentation."
The thing that bothers me much is that the VPN scarcely disconnects, only a single packet drop forces the merge agent to retry!!!. To isolate the problem i started ping reqest from publisher to subscriber; i saw merge agent to fail when a packet loss occured for only one second. VPN did not disconnect.
Currently i've chosen "slow link" profile for merge agent.
I started the snapshot 2 days ago and it restarts after every 2 or 3 hours.
Why the heck merge agent starts from the beginning; couldn't it be handled to start where it was when the connection was lost? Packet-loss is normal on the internet connections. I would love to know how u people replicate VLDBs over the internet.
I tried dynamic snapshot but found it rather risky; the merge agent stops with success during the middle of snapshot if connection is dropped leaving the subscriber with inconsistent data.
Any ideas and tips would be very much appreciated.
Howdy!I need u Guys!! :(|||An awful lot depends on what got lost, and where it got lost in the process. Merge replication is also a hodge-podge kind of thing, it is usually "interesting" trying to figure out where the "beginning" of it is, since it scarcely differentiates the difference between tables, much less any order to their changes.
Connections are definitely not "parts is parts" around the world. A connection from one part of the US to another is frequently "rock solid". A connection from here to London is very nearly as good, as is one from London to Sydney. One from the United States to Sydney is absolutely awful. So, we move the data going to Sydney through London... Even though it ends up going most of the way around the world instead of only about one fourth of the way, it is still ots more reliable.
Unless you have lots of time, energy, and money, this is where I'd bring in the "hired guns" to solve the problem. If you bring in someone like Microsoft Professional Services that deals with the various IP providers, knows the problems that exist between point A and point B, and understands the way that your specific replication setup is configured, you'll get an answer much faster and in the long run cheaper than trying to find the solution yourself.
-PatP|||Hi, Pat. Thanx for ur feedback.
I've tried this thing.
Publisher name SERVER1
Subscriber name SERVER2
I uploaded the SNAPSHOT.CAB (300 MB) from the publisher using download manager (if connection disconnects, it resumes where the connection was lost). It got uploaded in 3 hours.
Now i dropped the push merge subscription. Created Pull merge subscription at SERVER2. Placed the SNAPSHOT.CAB into local C drive of SERVER2.
The location i've extracted the snapshot file is:
C:\unc\SERVER1_MBDB_MBDB_PUBLICATION\2004061923325 2
In the Snapshot Location dialogbox for pull merge agent, I specified this location to force the agent to pick snapshot locally.
When i run the merge agent; it fails, for it searches the snapshot files from the default location at the publisher rather than the one i specified :mad: . The error is:
The schema script '\\SERVER1\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SERVER1_MBDB_MBDB_PUBLIC ATION\20040619233252\UR_TABLE_1.sch' could not be propagated to the subscriber.
Could not find the cabinet file 'snapshot.cab' in folder 'c:\unc\SERVER1_MBDB_MBDB_PUBLICATION\200406192332 52\unc\SERVER1_MBDB_MBDB_PUBLICATION\2004061923325 2\'
How can i square this location problem.
Any Help!!
Thanx for bearing along!|||If you are using a Merge PULL subscription, check the subscription properties at the subscriber to be sure that they specify the correct directory.
I'm a bit nervous about making suggestions, since you are making some pretty significant changes to what you are doing (push versus pull, where the agent exectutes, etc). Be careful to think out what you are doing!
-PatP|||Hi, thanx again 4 ur reply.
I did specify the correct directory where i placed the snapshot files. But the merge agent tries to access the snapshot from publisher's default directory rather than the local path.
I am tryin to use pull instead of push, for push won't work in my case due to disconnection. However i could move the whole snapshot.cab file to subscriber using a download manager despite the connection is lost b/w the transfer. But it isn't working either here. :confused:
Labels:
connection,
database,
duplex,
gurus,
internet,
mad,
merge,
microsoft,
mysql,
oracle,
outsnapshot,
plz,
publisher,
push,
replication,
server,
size,
sql,
subscriber,
subscription
Monday, March 12, 2012
Replication over the internet problems
I have a situation where a customer has a SQL 2000 database at thier office
location, this is where they do data updates, it replicates to a SQL 2000
server located at a web hosting facility. Problem is there is a new IT guy
at the office location that has done something to the setup so that now the
database does not replicate. When at the office you can see the hosting
facility SQL in SQL Manager but you can not see the SQL server from the
office location in the hosting facility. The SQL ports are open on the
firewall, and we can telnet to the port but it does not replicate and we can
not see the server in SQL Manager from the hosting facility. What should I
look at first?
Lee - check to see that the alias has not been removed - see (iii) here:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||I made the change on the ALIAS on the pull network and opened port 21 inbound
on the Push network. Replication seems successful on one Agent but there
seems to be an invalid Column error on the other. I am having the database
guys look at that. But this may have fixed the problem.
Thanks
|||The replication caused issues with the database. What I would like to do now
is remove everything and start from scratch. What things should I look for
first befoer removeing everything?
All we want to replicate is the data only, not schema or anything else.
Thansk.
|||Lee - if you have plain transactional replication using
sp_removedbreplication on the subscriber and dropping the publication at the
publisher should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Ok. I just got off the phone with Microsoft and I understand a lot now. Now
to test replication here is what we did:
Created a new database on the Publisher and added a table with columns and
data.
We then created a New Publication set. After creating this here is what
happened that has me stumped...
It created the database and the columns, but it did not replicate the data.
It gives and error: Generic Network error.
Some howit seems to be losing connection, maybe? Any ideas?
|||Lee,
I'd enable logging (http://support.microsoft.com/?id=312292) and see if this
gives more info. Also start ping -t before syncing to test connectivity.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
location, this is where they do data updates, it replicates to a SQL 2000
server located at a web hosting facility. Problem is there is a new IT guy
at the office location that has done something to the setup so that now the
database does not replicate. When at the office you can see the hosting
facility SQL in SQL Manager but you can not see the SQL server from the
office location in the hosting facility. The SQL ports are open on the
firewall, and we can telnet to the port but it does not replicate and we can
not see the server in SQL Manager from the hosting facility. What should I
look at first?
Lee - check to see that the alias has not been removed - see (iii) here:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||I made the change on the ALIAS on the pull network and opened port 21 inbound
on the Push network. Replication seems successful on one Agent but there
seems to be an invalid Column error on the other. I am having the database
guys look at that. But this may have fixed the problem.
Thanks
|||The replication caused issues with the database. What I would like to do now
is remove everything and start from scratch. What things should I look for
first befoer removeing everything?
All we want to replicate is the data only, not schema or anything else.
Thansk.
|||Lee - if you have plain transactional replication using
sp_removedbreplication on the subscriber and dropping the publication at the
publisher should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Ok. I just got off the phone with Microsoft and I understand a lot now. Now
to test replication here is what we did:
Created a new database on the Publisher and added a table with columns and
data.
We then created a New Publication set. After creating this here is what
happened that has me stumped...
It created the database and the columns, but it did not replicate the data.
It gives and error: Generic Network error.
Some howit seems to be losing connection, maybe? Any ideas?
|||Lee,
I'd enable logging (http://support.microsoft.com/?id=312292) and see if this
gives more info. Also start ping -t before syncing to test connectivity.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Labels:
customer,
database,
internet,
microsoft,
mysql,
officelocation,
oracle,
replicates,
replication,
server,
situation,
sql,
thier,
updates
Replication over the Internet - Resolving server name
We are using anonymouse pull subscriptions over the internet. We are not
using VPN.
The physical SQL Server is called SQL22Server. We have a Domain assigned to
it called something like company.com.
However, I found that on the client machine, I had to put in a hosts entry
to route SQL22Server to the IP address. I was hoping I could just use the
domain name.
This creates an administrative overhead because we have to do add a host
entry during the client install instead of having just assigning value to the
merge object.
If I try the domain, the error I get is: The remote server does not exist or
has not been designated as a valid Publisher.
I created the replication using the SQL22Server name.
Thanks,
Buzz
use the activeX scripts to deploy your subscriptions. In it there are
PublisherNetwork, DistributorNetwork, PublisherAddress, and
DistributorAddress properties. These map to the entries you would otherwise
put in your CNU or hosts file to make this work.
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
"Buzz" <buzz@.online.nospam> wrote in message
news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> We are using anonymouse pull subscriptions over the internet. We are not
> using VPN.
> The physical SQL Server is called SQL22Server. We have a Domain assigned
to
> it called something like company.com.
> However, I found that on the client machine, I had to put in a hosts entry
> to route SQL22Server to the IP address. I was hoping I could just use the
> domain name.
> This creates an administrative overhead because we have to do add a host
> entry during the client install instead of having just assigning value to
the
> merge object.
> If I try the domain, the error I get is: The remote server does not exist
or
> has not been designated as a valid Publisher.
> I created the replication using the SQL22Server name.
> Thanks,
> Buzz
|||Thanks for the quick reply.
I am publishing what I found for the newsgroup.
For us, the publisher and the distributer are the same machine. We are using
FTP for the initial snapshot. We are using SQL Server 2000 SP4 on the server
and MSDE SP4 on the laptop subscribers.
I found I did not need the distributer values because my distributer and
publisher where the same machine. I will most likely set them anyway so that
someday in production I can have a different distributer.
Here are the subscriber properties of the Merge object:
.Distributor = "SQL22Server"
.DistributorSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.DistributorAddress = "company.com"
.DistributorNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.DistributorLogin = "login"
.DistributorPassword = "password"
.Publisher = "SQL22Server"
.PublisherAddress = "company.com"
.PublisherDatabase = "data"
.PublisherNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.Publication = "data"
.PublisherSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.PublisherLogin = "login"
.PublisherPassword = "password"
The one last thing to make sure is that when setting up the FTP on the
server, use the PublisherAddress value. So "company.com" so that the
subscriber hits ftp://company.com/.
Also if you do this in production be careful the change to the FTP address
causes the publication to force a recreation of the initial snapshot.
Thanks,
Buzz
"Hilary Cotter" wrote:
> use the activeX scripts to deploy your subscriptions. In it there are
> PublisherNetwork, DistributorNetwork, PublisherAddress, and
> DistributorAddress properties. These map to the entries you would otherwise
> put in your CNU or hosts file to make this work.
> --
> 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
> "Buzz" <buzz@.online.nospam> wrote in message
> news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> to
> the
> or
>
>
|||Hi Buzz,
It looks more than a network issue.
- Could you PING SQL22Server from client and get the response?
- Could you telnet SQL22Server from client use the command like below
telnet <SQL22Server Domain Name>: 1433
- Do you have firewall between server and client? Have you open the TCP
port for them?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
using VPN.
The physical SQL Server is called SQL22Server. We have a Domain assigned to
it called something like company.com.
However, I found that on the client machine, I had to put in a hosts entry
to route SQL22Server to the IP address. I was hoping I could just use the
domain name.
This creates an administrative overhead because we have to do add a host
entry during the client install instead of having just assigning value to the
merge object.
If I try the domain, the error I get is: The remote server does not exist or
has not been designated as a valid Publisher.
I created the replication using the SQL22Server name.
Thanks,
Buzz
use the activeX scripts to deploy your subscriptions. In it there are
PublisherNetwork, DistributorNetwork, PublisherAddress, and
DistributorAddress properties. These map to the entries you would otherwise
put in your CNU or hosts file to make this work.
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
"Buzz" <buzz@.online.nospam> wrote in message
news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> We are using anonymouse pull subscriptions over the internet. We are not
> using VPN.
> The physical SQL Server is called SQL22Server. We have a Domain assigned
to
> it called something like company.com.
> However, I found that on the client machine, I had to put in a hosts entry
> to route SQL22Server to the IP address. I was hoping I could just use the
> domain name.
> This creates an administrative overhead because we have to do add a host
> entry during the client install instead of having just assigning value to
the
> merge object.
> If I try the domain, the error I get is: The remote server does not exist
or
> has not been designated as a valid Publisher.
> I created the replication using the SQL22Server name.
> Thanks,
> Buzz
|||Thanks for the quick reply.
I am publishing what I found for the newsgroup.
For us, the publisher and the distributer are the same machine. We are using
FTP for the initial snapshot. We are using SQL Server 2000 SP4 on the server
and MSDE SP4 on the laptop subscribers.
I found I did not need the distributer values because my distributer and
publisher where the same machine. I will most likely set them anyway so that
someday in production I can have a different distributer.
Here are the subscriber properties of the Merge object:
.Distributor = "SQL22Server"
.DistributorSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.DistributorAddress = "company.com"
.DistributorNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.DistributorLogin = "login"
.DistributorPassword = "password"
.Publisher = "SQL22Server"
.PublisherAddress = "company.com"
.PublisherDatabase = "data"
.PublisherNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.Publication = "data"
.PublisherSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.PublisherLogin = "login"
.PublisherPassword = "password"
The one last thing to make sure is that when setting up the FTP on the
server, use the PublisherAddress value. So "company.com" so that the
subscriber hits ftp://company.com/.
Also if you do this in production be careful the change to the FTP address
causes the publication to force a recreation of the initial snapshot.
Thanks,
Buzz
"Hilary Cotter" wrote:
> use the activeX scripts to deploy your subscriptions. In it there are
> PublisherNetwork, DistributorNetwork, PublisherAddress, and
> DistributorAddress properties. These map to the entries you would otherwise
> put in your CNU or hosts file to make this work.
> --
> 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
> "Buzz" <buzz@.online.nospam> wrote in message
> news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> to
> the
> or
>
>
|||Hi Buzz,
It looks more than a network issue.
- Could you PING SQL22Server from client and get the response?
- Could you telnet SQL22Server from client use the command like below
telnet <SQL22Server Domain Name>: 1433
- Do you have firewall between server and client? Have you open the TCP
port for them?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Labels:
anonymouse,
database,
domain,
internet,
microsoft,
mysql,
notusing,
oracle,
physical,
pull,
replication,
resolving,
server,
sql,
sql22server,
subscriptions,
vpn
Replication over the internet
Hi All,
Can I replicate from one sql server to another over the internet?
Regards,
Mekim
sure can. By default SQL Server communicates using port 1433. You will have
to deploy your snapshots using ftp.
If you are using MSDE subscribers the best way to deploy them is by using
anonymous subscriptions and use the activeX objects. Fill in values for
PublisherAddress, DistributorAddress, and PublisherNetwork and
DistributorNetwork.
"mekim" <mekim@.discussions.microsoft.com> wrote in message
news:4004177D-6C38-4F78-A812-3CFCB2F69C7A@.microsoft.com...
> Hi All,
> Can I replicate from one sql server to another over the internet?
> Regards,
> Mekim
|||THX!
"Hilary Cotter" wrote:
> sure can. By default SQL Server communicates using port 1433. You will have
> to deploy your snapshots using ftp.
> If you are using MSDE subscribers the best way to deploy them is by using
> anonymous subscriptions and use the activeX objects. Fill in values for
> PublisherAddress, DistributorAddress, and PublisherNetwork and
> DistributorNetwork.
> "mekim" <mekim@.discussions.microsoft.com> wrote in message
> news:4004177D-6C38-4F78-A812-3CFCB2F69C7A@.microsoft.com...
>
>
|||These links should help:
http://support.microsoft.com/?id=321822
http://www.microsoft.com/technet/tre...odtechnol/sql/
reskit/sql7res/part5/sqc07.asp
http://support.microsoft.com/default...32&Product=sql
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||THANK YOU!!!!
"Paul Ibison" wrote:
> These links should help:
> http://support.microsoft.com/?id=321822
> http://www.microsoft.com/technet/tre...odtechnol/sql/
> reskit/sql7res/part5/sqc07.asp
> http://support.microsoft.com/default...32&Product=sql
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Can I replicate from one sql server to another over the internet?
Regards,
Mekim
sure can. By default SQL Server communicates using port 1433. You will have
to deploy your snapshots using ftp.
If you are using MSDE subscribers the best way to deploy them is by using
anonymous subscriptions and use the activeX objects. Fill in values for
PublisherAddress, DistributorAddress, and PublisherNetwork and
DistributorNetwork.
"mekim" <mekim@.discussions.microsoft.com> wrote in message
news:4004177D-6C38-4F78-A812-3CFCB2F69C7A@.microsoft.com...
> Hi All,
> Can I replicate from one sql server to another over the internet?
> Regards,
> Mekim
|||THX!
"Hilary Cotter" wrote:
> sure can. By default SQL Server communicates using port 1433. You will have
> to deploy your snapshots using ftp.
> If you are using MSDE subscribers the best way to deploy them is by using
> anonymous subscriptions and use the activeX objects. Fill in values for
> PublisherAddress, DistributorAddress, and PublisherNetwork and
> DistributorNetwork.
> "mekim" <mekim@.discussions.microsoft.com> wrote in message
> news:4004177D-6C38-4F78-A812-3CFCB2F69C7A@.microsoft.com...
>
>
|||These links should help:
http://support.microsoft.com/?id=321822
http://www.microsoft.com/technet/tre...odtechnol/sql/
reskit/sql7res/part5/sqc07.asp
http://support.microsoft.com/default...32&Product=sql
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||THANK YOU!!!!
"Paul Ibison" wrote:
> These links should help:
> http://support.microsoft.com/?id=321822
> http://www.microsoft.com/technet/tre...odtechnol/sql/
> reskit/sql7res/part5/sqc07.asp
> http://support.microsoft.com/default...32&Product=sql
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Replication over the internet
I want to be able to replicate large volumes of data over the Internet
between SQL Server 2000 databases. The transmissions would be once per day,
need to be secure, and are to a location three time zones away.
What do you recommend for testing, security, support (the whole nine yards)?
TIA George
Ideally you should use a VPN for truly secure solutions. For testing you
would have to use representative loads and representative hardware. Support
is a tough one, as the problems you will see tend to be environment and
application specific.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"George Morton" <gmorton1@.optonline.net> wrote in message
news:k1GAd.18165$lU1.13967@.fe09.lga...
> I want to be able to replicate large volumes of data over the Internet
> between SQL Server 2000 databases. The transmissions would be once per
day,
> need to be secure, and are to a location three time zones away.
> What do you recommend for testing, security, support (the whole nine
yards)?
> TIA George
>
between SQL Server 2000 databases. The transmissions would be once per day,
need to be secure, and are to a location three time zones away.
What do you recommend for testing, security, support (the whole nine yards)?
TIA George
Ideally you should use a VPN for truly secure solutions. For testing you
would have to use representative loads and representative hardware. Support
is a tough one, as the problems you will see tend to be environment and
application specific.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"George Morton" <gmorton1@.optonline.net> wrote in message
news:k1GAd.18165$lU1.13967@.fe09.lga...
> I want to be able to replicate large volumes of data over the Internet
> between SQL Server 2000 databases. The transmissions would be once per
day,
> need to be secure, and are to a location three time zones away.
> What do you recommend for testing, security, support (the whole nine
yards)?
> TIA George
>
Labels:
database,
databases,
internet,
internetbetween,
microsoft,
mysql,
oracle,
replicate,
replication,
server,
sql,
transmissions,
volumes
Replication Over Internet via FTP
What is the syntax for the snapshop location setup referring to the "Client
path to this folder from the FTP root"? When my pull connects, it doesn't
seem to issue any change directory commands and does not find the snapshot
files which are there.
The client path is the path from the FTP root directory, so if your snapshot
directory is called TRSnapshot and is in the ftp root directory, the path
would be \TRSnapshot\ftp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks, worked like a charm but my main issue turned out to be the space in
the order details table in the Northwind db. I am doing a proof of concept
with that DB and it tried to run that script first and bombed.
"Paul Ibison" wrote:
> The client path is the path from the FTP root directory, so if your snapshot
> directory is called TRSnapshot and is in the ftp root directory, the path
> would be \TRSnapshot\ftp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Jeffrey,
this isn't such a large table - at what point does it fail?
Might be worth using the compression if you have a slow link?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
path to this folder from the FTP root"? When my pull connects, it doesn't
seem to issue any change directory commands and does not find the snapshot
files which are there.
The client path is the path from the FTP root directory, so if your snapshot
directory is called TRSnapshot and is in the ftp root directory, the path
would be \TRSnapshot\ftp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks, worked like a charm but my main issue turned out to be the space in
the order details table in the Northwind db. I am doing a proof of concept
with that DB and it tried to run that script first and bombed.
"Paul Ibison" wrote:
> The client path is the path from the FTP root directory, so if your snapshot
> directory is called TRSnapshot and is in the ftp root directory, the path
> would be \TRSnapshot\ftp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Jeffrey,
this isn't such a large table - at what point does it fail?
Might be worth using the compression if you have a slow link?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
replication over internet
Hi
I want to set up a replication between servers over the internet. I know
there are 3 ways to do this, using VPN,proxy server or TCP/IP (FTP). but I
don't know the advantages of each one. could you tell me what are the
differences between these ways in performance and security?
and could you tell me what will happen if the servers disconnect from each
other during the process of replication?
Thanks
Tajik,
connectivity is really a choice between VPN or non-trusted connectivity. The
way I see these breaking down are...
using a VPN is secure and you'll be able to use fileshares ie there's no
need to enable FTP. So, although you're operating over the internet things
are much the same as per usual.
The proxy server is an element of the connectivity to a network by acting as
a firewall and blocking traffic on non-essential ports, and possibly
allowing traffic from only assigned IP addresses.
TCP/IP & FTP is the method used if you are replicating across non-trusted
domains - ie in the absence of a VPN. You can have it operate securely by
using a certificate and encrypting the TCP/IP traffic.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul, I am getting the following error when I attempt to download the
snapshot files from the Replication FTP Site:
Date11/30/2005 1:20:22 PM
LogJob History
(28053-DB-inventory_master-inventory_master_a-S-HUNLEY-inventory_master-5007D5E3-0C82-47A1-A26A-5E8F52E68F83)
Step ID1
ServerS-HUNLEY
Job
Name28053-DB-inventory_master-inventory_master_a-S-HUNLEY-inventory_master-5007D5E3-0C82-47A1-A26A-5E8F52E68F83
Step NameRun agent.
Duration00:20:24
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
-XSERVER S-HUNLEY
-XCMDLINE 0
-XCancelEventHandle 00000828
2005-11-30 18:40:37.661 Startup Delay: 4093 (msecs)
2005-11-30 18:40:41.757 Connecting to Subscriber 'S-HUNLEY'
2005-11-30 18:40:42.008 Connecting to Distributor '28053-DB'
2005-11-30 18:40:42.729 Initializing
2005-11-30 18:40:42.919 Parameter values obtained from agent profile:
-bcpbatchsize 100000
-commitbatchsize 100
-commitbatchthreshold 1000
-historyverboselevel 1
-keepalivemessageinterval 300
-logintimeout 15
-maxbcpthreads 1
-maxdeliveredtransactions 0
-pollinginterval 10000
-querytimeout 300
-skiperrors
-transactionsperhistory 100
2005-11-30 18:40:44.121 Snapshot files will be downloaded via ftp
2005-11-30 18:40:44.301 Connecting to ftp site '28053-DB'
2005-11-30 18:40:46.334 Agent message code 20033. The process could not
retrieve file
'28053-DB_inventory_master_inventory_master_articles\2005 1130120007\Purchase_Order_Line_Items_1.sch' from the FTP site '28053-DB'.
The Publisher is a SQL Server 2000 Database (SP3A) running on Windows 2000
Advanced Server and the Subscriber is a SQL Server 2005 database running on
Windows XP Pro SP2. These databases on in diferent domains. I can ping the
machines from one another and I can see the FTP folder from the subscriber as
well as on the publisher.
Any ideas?
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:
> Tajik,
> connectivity is really a choice between VPN or non-trusted connectivity. The
> way I see these breaking down are...
> using a VPN is secure and you'll be able to use fileshares ie there's no
> need to enable FTP. So, although you're operating over the internet things
> are much the same as per usual.
> The proxy server is an element of the connectivity to a network by acting as
> a firewall and blocking traffic on non-essential ports, and possibly
> allowing traffic from only assigned IP addresses.
> TCP/IP & FTP is the method used if you are replicating across non-trusted
> domains - ie in the absence of a VPN. You can have it operate securely by
> using a certificate and encrypting the TCP/IP traffic.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Scott,
perhaps it is the path you are using to the ftp folder.
When I set this up I used the path
'c:\inetpub\ftproot\trsnapshot'
as the alternative snapshot location on the publisher (snapshot location
tab) - and
\trsnapshot\ftp
as the 'client path to this folder'.
Pls can you tell us what are the corresponding settings on your publisher.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I have the following settings in my Publisher:
Alternate Path (Default Path unchecked) -
'\\28053-DB\D$\inetpub\ftproot\replication\inventory_master \'
Ftp Client path -
'\replication\inventory_master\'
The Server that I remote into, automatically assigns the \\28053-DB\D$\
qualifier. I didn't include the ftp subdirectory that you did, it was
created by the process however.
Is this explanation concise enough? If more details are needed please let
me know and I will provide them ASAP.
Thanks in advance for any help or advice you might have.
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:
> Scott,
> perhaps it is the path you are using to the ftp folder.
> When I set this up I used the path
> 'c:\inetpub\ftproot\trsnapshot'
> as the alternative snapshot location on the publisher (snapshot location
> tab) - and
> \trsnapshot\ftp
> as the 'client path to this folder'.
> Pls can you tell us what are the corresponding settings on your publisher.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Paul, by the time I was finished writing the first post/response.. I realized
what i had done wrong. I had forgot to put the subdirectory /ftp/ in my
Client Ftp path. Once i did, I reran the process and it worked. Now, I'm
not sure how well replication of anything other than the tables will work,
going from 2000 to 2005, but at least the Data Warehouse is populating
correctly, and transactionally.
I greatly appreciate your time and look forward to discussing other items in
the future.
Respectfully,
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:
> Scott,
> perhaps it is the path you are using to the ftp folder.
> When I set this up I used the path
> 'c:\inetpub\ftproot\trsnapshot'
> as the alternative snapshot location on the publisher (snapshot location
> tab) - and
> \trsnapshot\ftp
> as the 'client path to this folder'.
> Pls can you tell us what are the corresponding settings on your publisher.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
I want to set up a replication between servers over the internet. I know
there are 3 ways to do this, using VPN,proxy server or TCP/IP (FTP). but I
don't know the advantages of each one. could you tell me what are the
differences between these ways in performance and security?
and could you tell me what will happen if the servers disconnect from each
other during the process of replication?
Thanks
Tajik,
connectivity is really a choice between VPN or non-trusted connectivity. The
way I see these breaking down are...
using a VPN is secure and you'll be able to use fileshares ie there's no
need to enable FTP. So, although you're operating over the internet things
are much the same as per usual.
The proxy server is an element of the connectivity to a network by acting as
a firewall and blocking traffic on non-essential ports, and possibly
allowing traffic from only assigned IP addresses.
TCP/IP & FTP is the method used if you are replicating across non-trusted
domains - ie in the absence of a VPN. You can have it operate securely by
using a certificate and encrypting the TCP/IP traffic.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul, I am getting the following error when I attempt to download the
snapshot files from the Replication FTP Site:
Date11/30/2005 1:20:22 PM
LogJob History
(28053-DB-inventory_master-inventory_master_a-S-HUNLEY-inventory_master-5007D5E3-0C82-47A1-A26A-5E8F52E68F83)
Step ID1
ServerS-HUNLEY
Job
Name28053-DB-inventory_master-inventory_master_a-S-HUNLEY-inventory_master-5007D5E3-0C82-47A1-A26A-5E8F52E68F83
Step NameRun agent.
Duration00:20:24
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
-XSERVER S-HUNLEY
-XCMDLINE 0
-XCancelEventHandle 00000828
2005-11-30 18:40:37.661 Startup Delay: 4093 (msecs)
2005-11-30 18:40:41.757 Connecting to Subscriber 'S-HUNLEY'
2005-11-30 18:40:42.008 Connecting to Distributor '28053-DB'
2005-11-30 18:40:42.729 Initializing
2005-11-30 18:40:42.919 Parameter values obtained from agent profile:
-bcpbatchsize 100000
-commitbatchsize 100
-commitbatchthreshold 1000
-historyverboselevel 1
-keepalivemessageinterval 300
-logintimeout 15
-maxbcpthreads 1
-maxdeliveredtransactions 0
-pollinginterval 10000
-querytimeout 300
-skiperrors
-transactionsperhistory 100
2005-11-30 18:40:44.121 Snapshot files will be downloaded via ftp
2005-11-30 18:40:44.301 Connecting to ftp site '28053-DB'
2005-11-30 18:40:46.334 Agent message code 20033. The process could not
retrieve file
'28053-DB_inventory_master_inventory_master_articles\2005 1130120007\Purchase_Order_Line_Items_1.sch' from the FTP site '28053-DB'.
The Publisher is a SQL Server 2000 Database (SP3A) running on Windows 2000
Advanced Server and the Subscriber is a SQL Server 2005 database running on
Windows XP Pro SP2. These databases on in diferent domains. I can ping the
machines from one another and I can see the FTP folder from the subscriber as
well as on the publisher.
Any ideas?
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:
> Tajik,
> connectivity is really a choice between VPN or non-trusted connectivity. The
> way I see these breaking down are...
> using a VPN is secure and you'll be able to use fileshares ie there's no
> need to enable FTP. So, although you're operating over the internet things
> are much the same as per usual.
> The proxy server is an element of the connectivity to a network by acting as
> a firewall and blocking traffic on non-essential ports, and possibly
> allowing traffic from only assigned IP addresses.
> TCP/IP & FTP is the method used if you are replicating across non-trusted
> domains - ie in the absence of a VPN. You can have it operate securely by
> using a certificate and encrypting the TCP/IP traffic.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Scott,
perhaps it is the path you are using to the ftp folder.
When I set this up I used the path
'c:\inetpub\ftproot\trsnapshot'
as the alternative snapshot location on the publisher (snapshot location
tab) - and
\trsnapshot\ftp
as the 'client path to this folder'.
Pls can you tell us what are the corresponding settings on your publisher.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I have the following settings in my Publisher:
Alternate Path (Default Path unchecked) -
'\\28053-DB\D$\inetpub\ftproot\replication\inventory_master \'
Ftp Client path -
'\replication\inventory_master\'
The Server that I remote into, automatically assigns the \\28053-DB\D$\
qualifier. I didn't include the ftp subdirectory that you did, it was
created by the process however.
Is this explanation concise enough? If more details are needed please let
me know and I will provide them ASAP.
Thanks in advance for any help or advice you might have.
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:
> Scott,
> perhaps it is the path you are using to the ftp folder.
> When I set this up I used the path
> 'c:\inetpub\ftproot\trsnapshot'
> as the alternative snapshot location on the publisher (snapshot location
> tab) - and
> \trsnapshot\ftp
> as the 'client path to this folder'.
> Pls can you tell us what are the corresponding settings on your publisher.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Paul, by the time I was finished writing the first post/response.. I realized
what i had done wrong. I had forgot to put the subdirectory /ftp/ in my
Client Ftp path. Once i did, I reran the process and it worked. Now, I'm
not sure how well replication of anything other than the tables will work,
going from 2000 to 2005, but at least the Data Warehouse is populating
correctly, and transactionally.
I greatly appreciate your time and look forward to discussing other items in
the future.
Respectfully,
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"Paul Ibison" wrote:
> Scott,
> perhaps it is the path you are using to the ftp folder.
> When I set this up I used the path
> 'c:\inetpub\ftproot\trsnapshot'
> as the alternative snapshot location on the publisher (snapshot location
> tab) - and
> \trsnapshot\ftp
> as the 'client path to this folder'.
> Pls can you tell us what are the corresponding settings on your publisher.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
Replication over Internet
I want to create merge publication between Server A(publisher) and Client
B(subscriber) over Internet. However, because of the security reasons Server
A cannot be directly accessed over Internet. What is the solution for this
case?
If I seperate distrbutor from Server A and enable it to be accessed directly
over Internet and Client B subscribes through distrbutor can this be a
solution?
(VPN is not allowed)
Erkan,
as far as I understand, the merge agent will need connectivity between the
publisher and subscriber to read the MSmerge_contents and MSmerge_tombstone
tables on each box, and the absence of any connectivity will preclude this
from working. However, you could investigate republishing to achieve your
goal.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
B(subscriber) over Internet. However, because of the security reasons Server
A cannot be directly accessed over Internet. What is the solution for this
case?
If I seperate distrbutor from Server A and enable it to be accessed directly
over Internet and Client B subscribes through distrbutor can this be a
solution?
(VPN is not allowed)
Erkan,
as far as I understand, the merge agent will need connectivity between the
publisher and subscriber to read the MSmerge_contents and MSmerge_tombstone
tables on each box, and the absence of any connectivity will preclude this
from working. However, you could investigate republishing to achieve your
goal.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Labels:
clientb,
create,
database,
internet,
merge,
microsoft,
mysql,
oracle,
publication,
publisher,
replication,
security,
server,
sql,
subscriber
Subscribe to:
Posts (Atom)