Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / July 2006

Tip: Looking for answers? Try searching our database.

sql 2000 publishing/subscribing using ftp... is what I'm trying possible?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
krackq - 28 Jul 2006 17:04 GMT
We have an sql server (server A) at a supplier that is windows 2003,
running sql server 2000.  Its only connection to the outside world is
via normal internet access as any other pc there.

Now, at our facility here (which is completely separate from theirs) we
have an sql server (Server B) on windows 2003 server, running sql
server 2000 that has its ftp port publicly accessible... that is, files
can be ftp'ed into a directory on that server from the internet.

Can set up replication between the two servers.  That is, can I
basically replicate a database on a regular basis from Server A to
Server B so that the database on Server B is more or less an updated
copy of the one on Server A?  We're looking to be able to do reporting
on the database on server A by having a copy of it on Server B at our
facility (because server a is not available to anyone here).

I've tried playing with a lot of the publication settings etc.  The
best I can figure out is how to make a snapshot of the database on
Server A into a local ftp directory on Server A (keep in mind that even
though Server A has ftp on it, its not available to anyone outside the
company.. so I guess its, in effect, snapshotting just to a local
folder).  From there I can ftp the files to Server B since B has ftp
services available.   Now.. from here, I'm pretty much stuck.  I dont'
know how to subscribe (or even if I can) to these ftp'ed files.

Is there a particular way I need to configure things on the publishing
server.. and/or the subscribing server?  Or am I trying to do something
not possible here?  I'm open for suggestions too as this is something I
have to figure out.   The whole idea is keeping a copy of Server A's
database up to date here on Server B so we can run reporting against
it.

Thanks!!
Hilary Cotter - 28 Jul 2006 22:59 GMT
What does normal internet access mean? Port 80? Can it access the publisher
over port 1433? It doesn't sound like it. In fact it sounds like it can only
access port 21 (ftp). You will need to run your Publisher on port 21, and
have another ftp server running on port 21 which your publisher copies the
snapshot files to this ftp server.

When you create your publication right click on it, select snapshot location
and here configure the other ftp server.

Now your subscriber will access this ftp server to pull the snapshot.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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

> We have an sql server (server A) at a supplier that is windows 2003,
> running sql server 2000.  Its only connection to the outside world is
[quoted text clipped - 29 lines]
>
> Thanks!!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.