Replication over VPN

I am new to both replication & VPN setup.
I've been asked to replicate a DB from WinXP SP2 to Server 2003 over a VPN.
Both machines are running SQL 2000 3a.
The VPN appears setup correctly (almost) - I can ping both ends and name
resolution is OK. However, I can't browse the server shares from the PC or
vice versa.
In Ent Man I can connect to the servers on both machines but browsing the DB
tables is very slow and most often results in general network failure errors.
Questions:
1. Will SQL Server operate over a VPN or does port 1433 have to be open at
the firewall?
2. I have tried setting up Snapshot Replication with Push Subscription
without success. What is the simplest way to achieve the goal of copying the
DB from XP to the server on a regular basis?
Thank you.
1 )Replication does work over a VPN, but as you have found out it does take
longer than if you were replicating locally over a LAN/WAN.
2) set LoginTimeout and QueryTimeout to large values. The fact that you
can't browse server shares to me indicates that the RPC ports aren't open.
In this case you will probably have to use FTP will a pull subscription.
"MikeH" <MikeH@.community.nospam> wrote in message
news:79A546ED-8473-4BED-9508-501EF601AE86@.microsoft.com...
>I am new to both replication & VPN setup.
> I've been asked to replicate a DB from WinXP SP2 to Server 2003 over a
> VPN.
> Both machines are running SQL 2000 3a.
> The VPN appears setup correctly (almost) - I can ping both ends and name
> resolution is OK. However, I can't browse the server shares from the PC or
> vice versa.
> In Ent Man I can connect to the servers on both machines but browsing the
> DB
> tables is very slow and most often results in general network failure
> errors.
> Questions:
> 1. Will SQL Server operate over a VPN or does port 1433 have to be open at
> the firewall?
> 2. I have tried setting up Snapshot Replication with Push Subscription
> without success. What is the simplest way to achieve the goal of copying
> the
> DB from XP to the server on a regular basis?
> Thank you.
>
|||Hilary
Thank you for the response. The recuperative power of a server reboot is
truly amazing. I can now browse shares and replicate servers.
"Hilary Cotter" wrote:

> 1 )Replication does work over a VPN, but as you have found out it does take
> longer than if you were replicating locally over a LAN/WAN.
> 2) set LoginTimeout and QueryTimeout to large values. The fact that you
> can't browse server shares to me indicates that the RPC ports aren't open.
> In this case you will probably have to use FTP will a pull subscription.
> "MikeH" <MikeH@.community.nospam> wrote in message
> news:79A546ED-8473-4BED-9508-501EF601AE86@.microsoft.com...
>
>

Replication on MSDE2000 and db size problem

Hi,
We have following scenario:
2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
failover backup. DBs are connected by merge replication where backup is as
subscriber.
The problem is related to one table with binary column (2K) and its growing
size (over 100MB per day).
sp_spaceused product_map
name rows reserved data index_size unused
Product_map 24238 1056648KB 130448KB 13520KB 912640KB
It seems that on insert rows server allocates more space than need. This
problem occures only when system works on publisher db. It is ok when I
switch it to backup PC.
I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
don't observe the problem like this.
could you help me how to diagnose it more deeply and solve the problem?
Janek
A couple of points 1) are you using text in row?
2) Are you sure the data in this column is the same on the publisher and
subscriber. Depending on how you update your text or image data it may not
be replicated.
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
"Janek" <Janek@.discussions.microsoft.com> wrote in message
news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
> Hi,
> We have following scenario:
> 2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
> failover backup. DBs are connected by merge replication where backup is as
> subscriber.
> The problem is related to one table with binary column (2K) and its
> growing
> size (over 100MB per day).
> sp_spaceused product_map
> name rows reserved data index_size
> unused
> Product_map 24238 1056648KB 130448KB 13520KB 912640KB
> It seems that on insert rows server allocates more space than need. This
> problem occures only when system works on publisher db. It is ok when I
> switch it to backup PC.
> I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
> don't observe the problem like this.
> could you help me how to diagnose it more deeply and solve the problem?
> Janek
|||1) data type for table is: int, smallint, int, char(11), smallint, smallint,
binary(2001), bit, datetime, int
2) All data is replicating, I can see it on reports on each machines. From
sp_spaceused report I see almost 1GB of unused space.
I know only one workaround:
dbcc dbreindex (.... + shrink db - a few cycles makes db to similar
backup db size.
At the moment system is working on backup PC without problem and new data is
refreshed to publisher.
Janek
"Hilary Cotter" wrote:

> A couple of points 1) are you using text in row?
> 2) Are you sure the data in this column is the same on the publisher and
> subscriber. Depending on how you update your text or image data it may not
> be replicated.
> --
> 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
>
> "Janek" <Janek@.discussions.microsoft.com> wrote in message
> news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
>
>