Hi,
Please help, I am new to replication.
I have setup a vpn connection from one computer to another.
e.g. Computer X and computer Y. Both are in different area of the city.
Both computers have mssql 2000. The source database is in computer X.
I like to replicate the data in computer X to computer Y. In computer Y I
can see the X's mssql db. It is shown us 192.168.0.2 in EM.
which is the ip address use in the VPN for computer X. I cannot create the
replication because the computer name is shown as an ip address.
Is there a way to change it to the real computer name?
Can someone please point me to any articles or tutorials that may help me to
set up replication thru VPN or thru the Internet?
Thank You.
Sam
You could try making use of the HOSTS file on the servers to map IP and the
server name. Then try to register SQL servers from enterprise manager
- Sid
"sam" wrote:
> Hi,
> Please help, I am new to replication.
> I have setup a vpn connection from one computer to another.
> e.g. Computer X and computer Y. Both are in different area of the city.
> Both computers have mssql 2000. The source database is in computer X.
> I like to replicate the data in computer X to computer Y. In computer Y I
> can see the X's mssql db. It is shown us 192.168.0.2 in EM.
> which is the ip address use in the VPN for computer X. I cannot create the
> replication because the computer name is shown as an ip address.
> Is there a way to change it to the real computer name?
> Can someone please point me to any articles or tutorials that may help me to
> set up replication thru VPN or thru the Internet?
> Thank You.
> Sam
>
>
>
|||sam wrote:
> Both computers have mssql 2000. The source database is in computer X.
> I like to replicate the data in computer X to computer Y. In computer Y I
> can see the X's mssql db. It is shown us 192.168.0.2 in EM.
> which is the ip address use in the VPN for computer X. I cannot create the
> replication because the computer name is shown as an ip address.
> Is there a way to change it to the real computer name?
Use the Client Network Utility to give that IP an alias.
|||Thanks.
"Ryan Walberg [MCSD]" <generalpf@.nospam.yahoo.reallynospam.com> wrote in
message news:OyovrA9KFHA.2252@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> sam wrote:
I[vbcol=seagreen]
the
> Use the Client Network Utility to give that IP an alias.
Showing posts with label connection. Show all posts
Showing posts with label connection. Show all posts
Friday, March 30, 2012
Tuesday, March 20, 2012
Replication problem
Hi everyone!
I have a problem with my replication. I've done merge replication, I have
one publisher and one subscriber. The connection between servers is via ADSL.
The merge replication does fine, when there is an active connection. But
when the connection (ADSL) drops, my merge agent stops with an error.
I changed the attempt times and interval in minutes under merge job to 100
times on 10 minutes. But nothing helps. When the connection drops, I
immediately get the error:
Could not connect to Subscriber.
Could not generate SSPI context.
Any ideas?
If you have an unreliable connection, there's no quick/simple fix. You could
schedule your merge agent to run once a minute, or hardcode the job steps to
continue on failure.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I have a problem with my replication. I've done merge replication, I have
one publisher and one subscriber. The connection between servers is via ADSL.
The merge replication does fine, when there is an active connection. But
when the connection (ADSL) drops, my merge agent stops with an error.
I changed the attempt times and interval in minutes under merge job to 100
times on 10 minutes. But nothing helps. When the connection drops, I
immediately get the error:
Could not connect to Subscriber.
Could not generate SSPI context.
Any ideas?
If you have an unreliable connection, there's no quick/simple fix. You could
schedule your merge agent to run once a minute, or hardcode the job steps to
continue on failure.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
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:
Monday, March 12, 2012
Replication over VPN
I have a Delphi application that connects to SQL server 2K.
Recently another part of the company wanted to use the application, but the connection between us goes through a number of firewalls. The only solution that I have been able to come up with so far is for the new users to VPN into the server to use the application, but this is a real pain for them.
Is there an obvious alternative? No 're-write as a web app' please!
I have thought about setting the remote users up with a separatae server and then merge replicating betwen the two, but that would require a VPN connection to allow the replication to work (I presume). How would that work? What would open the VPN connection and close it after the replication was complete? What would happen to users that were connected at both the main server and the remote one when the VPN link was started?
Any thoughts gratefully received....Merge replication may require a complete redesign, unless your current design meets its requirements.|||Does the other division need both read and write access to the database? If not, you could transfer backups by sneakernet if nothing else.
Otherwise, talk to your network admins. It's their job to provide access through the firewalls for legitimate traffic. Better yet, get the head of the other division to expedite it.
Recently another part of the company wanted to use the application, but the connection between us goes through a number of firewalls. The only solution that I have been able to come up with so far is for the new users to VPN into the server to use the application, but this is a real pain for them.
Is there an obvious alternative? No 're-write as a web app' please!
I have thought about setting the remote users up with a separatae server and then merge replicating betwen the two, but that would require a VPN connection to allow the replication to work (I presume). How would that work? What would open the VPN connection and close it after the replication was complete? What would happen to users that were connected at both the main server and the remote one when the VPN link was started?
Any thoughts gratefully received....Merge replication may require a complete redesign, unless your current design meets its requirements.|||Does the other division need both read and write access to the database? If not, you could transfer backups by sneakernet if nothing else.
Otherwise, talk to your network admins. It's their job to provide access through the firewalls for legitimate traffic. Better yet, get the head of the other division to expedite it.
Replication over satelite connection.
Hi everybody, we are designing an application for ships, and I want to replicate data between the ships and a home office. TCP/IP communication is not possible, but we have a e-mail based system for transferring files.
What is the best solution? Is it possible to have the publisher/subscriber to leave a file, and then let the e-mail system transfer the file and then later the subscriber/publisher can pick up the file and do the merge?
Any ideas?
Thanx, Kjetil
Kjetil,
this is not directly possible in the replication setup. You might want to
use DTS to import the file into a database then in the DTS package. Setup
replication between this staging database and your central system and you
can initiate replication locally.
HTH,
Paul Ibison
|||Thanks, this is what I tried to say to my boss. But how can this be implemented? Should I use merge replication or transactional replication.
In my home office, I will need a 'copy' of the ship database, in the first stage 9 ships.
Is it possible to block the database in the ships for updates while the replication process is running?
Or should I use transactional replication, will I then need a 'proxy database' at each ship and one for each ship in the home office. Is it possible to implement conflict resolution methods that guarantee the same result at all sites always?
The amount of data over the satellite link (64k) is an issue, so it is important to send only the changes.
Do you think I'm on track? Is it possible to implement.
Kjetil
|||Kjso,
as you need inserts updates and deletes to be replicated over the internet,
you are essentially coding what MS developers may well be creating in SQL
2005 :-). This is not straightforward at all (to say the least). You might
want to use triggers on each table which write an audit of changes to your
audit table(s). These audit table changes are then sent over the link to a
central server where they are applied to the central database. In my opinion
this is only going to be feasible at the central server if you have
partitioned data; dealing with conflicts will make this too difficult. Then
sending only the changes required back to the other subscribers is not
simple. You say that you want only changes, but a 'snapshot' would be more
straightforward.
HTH,
Paul Ibison
What is the best solution? Is it possible to have the publisher/subscriber to leave a file, and then let the e-mail system transfer the file and then later the subscriber/publisher can pick up the file and do the merge?
Any ideas?
Thanx, Kjetil
Kjetil,
this is not directly possible in the replication setup. You might want to
use DTS to import the file into a database then in the DTS package. Setup
replication between this staging database and your central system and you
can initiate replication locally.
HTH,
Paul Ibison
|||Thanks, this is what I tried to say to my boss. But how can this be implemented? Should I use merge replication or transactional replication.
In my home office, I will need a 'copy' of the ship database, in the first stage 9 ships.
Is it possible to block the database in the ships for updates while the replication process is running?
Or should I use transactional replication, will I then need a 'proxy database' at each ship and one for each ship in the home office. Is it possible to implement conflict resolution methods that guarantee the same result at all sites always?
The amount of data over the satellite link (64k) is an issue, so it is important to send only the changes.
Do you think I'm on track? Is it possible to implement.
Kjetil
|||Kjso,
as you need inserts updates and deletes to be replicated over the internet,
you are essentially coding what MS developers may well be creating in SQL
2005 :-). This is not straightforward at all (to say the least). You might
want to use triggers on each table which write an audit of changes to your
audit table(s). These audit table changes are then sent over the link to a
central server where they are applied to the central database. In my opinion
this is only going to be feasible at the central server if you have
partitioned data; dealing with conflicts will make this too difficult. Then
sending only the changes required back to the other subscribers is not
simple. You say that you want only changes, but a 'snapshot' would be more
straightforward.
HTH,
Paul Ibison
Subscribe to:
Posts (Atom)