Replication across the internet

Hi,
I want to replicate my data with a sql server in internet(via dial-up
connection).
Do I necessarily need to use FTP for transferring the initial snapshots or
it is an alternate solution?
I saw this in article number '321822' in Microsoft's site, the second
example in this article mentions:
Example 2: The Subscriber Does Not Have the Schema and Data, and the Initial
Subscription from the Publisher Is Required.
This example requires you to configure the FTP service at the Publisher, and
then configure the Subscriber to download the initial snapshot from the FTP
site. For more information, see the following topics in SQL Server Books
Online...
Thanks in advance,
Amin
you don't need to. Somehow you need to get the schema and data to the
subscriber. You can't use a UNC, so you have to use FTP, or get them there
via mail, courier or some other system.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Amin Sobati" <amins@.morva.net> wrote in message
news:OddhXyBXEHA.3640@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I want to replicate my data with a sql server in internet(via dial-up
> connection).
> Do I necessarily need to use FTP for transferring the initial snapshots or
> it is an alternate solution?
> I saw this in article number '321822' in Microsoft's site, the second
> example in this article mentions:
> --
> Example 2: The Subscriber Does Not Have the Schema and Data, and the
Initial
> Subscription from the Publisher Is Required.
> This example requires you to configure the FTP service at the Publisher,
and
> then configure the Subscriber to download the initial snapshot from the
FTP
> site. For more information, see the following topics in SQL Server Books
> Online...
> --
> Thanks in advance,
> Amin
>
|||Hilary,
If I'm creating a push subscription, and my publisher is distributor too,
then I suppose the snapshot on my local hard drive can be used by merge
agent, is it correct?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OQ#8NYLXEHA.2844@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> you don't need to. Somehow you need to get the schema and data to the
> subscriber. You can't use a UNC, so you have to use FTP, or get them there
> via mail, courier or some other system.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:OddhXyBXEHA.3640@.TK2MSFTNGP11.phx.gbl...
or
> Initial
> and
> FTP
>
|||The distributor doesn't really factor into merge replication other than
being a repository where historical information is held.
You should be using a PULL subscription when you are replicating over the
internet. If you open the NetBIOS (IIRC) necessary for a push subscription
you are exposing your self to hackers.
"Amin Sobati" <amins@.morva.net> wrote in message
news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hilary,
> If I'm creating a push subscription, and my publisher is distributor too,
> then I suppose the snapshot on my local hard drive can be used by merge
> agent, is it correct?
> Thanks,
> Amin
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OQ#8NYLXEHA.2844@.TK2MSFTNGP11.phx.gbl...
there[vbcol=seagreen]
snapshots[vbcol=seagreen]
> or
Publisher,[vbcol=seagreen]
the[vbcol=seagreen]
Books
>
|||Hilary,
I'm only the owner of the database at subscriber, and there's some errors
while trying to create pull subscription. Our sql server host(subscriber)
has added my publisher name(computer name) as a remote server and mapped all
of our logins(local) to the login which was created at their sql server. But
still there're some error indicating the loss of permissions.
What's the best solution?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:#7ZT5bQXEHA.2364@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> The distributor doesn't really factor into merge replication other than
> being a repository where historical information is held.
> You should be using a PULL subscription when you are replicating over the
> internet. If you open the NetBIOS (IIRC) necessary for a push subscription
> you are exposing your self to hackers.
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...
too,[vbcol=seagreen]
> there
dial-up[vbcol=seagreen]
> snapshots
second
> Publisher,
> the
> Books
>
|||Hilary,
I'm only the owner of the database at subscriber, and there's some errors
while trying to create pull subscription. Our sql server host(subscriber)
has added my publisher name(computer name) as a remote server and mapped all
of our logins(local) to the login which was created at their sql server. But
still there're some error indicating the loss of permissions.
What's the best solution?
Thanks,
Amin
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:#7ZT5bQXEHA.2364@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> The distributor doesn't really factor into merge replication other than
> being a repository where historical information is held.
> You should be using a PULL subscription when you are replicating over the
> internet. If you open the NetBIOS (IIRC) necessary for a push subscription
> you are exposing your self to hackers.
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:O00$21NXEHA.3512@.TK2MSFTNGP12.phx.gbl...
too,[vbcol=seagreen]
> there
dial-up[vbcol=seagreen]
> snapshots
second
> Publisher,
> the
> Books
>

Replication - Preventing data deletion

I have just started using data replication as a method of transferring data
from a temporary database to a central one. This works fine however I wanted
to be able to clear down the temporary database from time to time but not
surprisingly this deletes the corresponding records from the main database.
Is it possible to prevent the deletion of records from the publisher removing
the corresponding records in the subscriber? How about changing the Delete
command with a procedure that does nothing in the Table Article Properties?
Thanks,
Bill
You can either change the Delete to do nothing in the Table Article
properties or, if you are using the replication stored procedures, you can
alter the delete procedure at the subscriber to do nothing.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Replication - Preventing data deletion

I have just started using data replication as a method of transferring data
from a temporary database to a central one. This works fine however I wante
d
to be able to clear down the temporary database from time to time but not
surprisingly this deletes the corresponding records from the main database.
Is it possible to prevent the deletion of records from the publisher removin
g
the corresponding records in the subscriber? How about changing the Delete
command with a procedure that does nothing in the Table Article Properties?
Thanks,
BillYou can either change the Delete to do nothing in the Table Article
properties or, if you are using the replication stored procedures, you can
alter the delete procedure at the subscriber to do nothing.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Replication - Preventing data deletion

I have just started using data replication as a method of transferring data
from a temporary database to a central one. This works fine however I wanted
to be able to clear down the temporary database from time to time but not
surprisingly this deletes the corresponding records from the main database.
Is it possible to prevent the deletion of records from the publisher removing
the corresponding records in the subscriber? How about changing the Delete
command with a procedure that does nothing in the Table Article Properties?
Thanks,
BillYou can either change the Delete to do nothing in the Table Article
properties or, if you are using the replication stored procedures, you can
alter the delete procedure at the subscriber to do nothing.
Rand
This posting is provided "as is" with no warranties and confers no rights.