Hello,
I am replicating databases from a sql2000 server with a
seperate distributer running sql2000 server and a MSDE subscriber. I
am using merge replication. The subscribers pull a subscription.
We want to have this setup across the internet for multiple
subscribers
each of whom might be updating as frequently as 1 hour. There are a
couple of issues I would like to find out about.
1.Security: I understood that the initial snapshots can be
published via ftp ( or any other means ofcourse). Can the merge
process be accomplished via ftp too? i.e The merge agent running on
the subscriber, writes to the ftp space reserved for it and the
publisher uses these files to bring the publisher up to speed and put
the updates back to all the subscribers. (sounds very slow). What are
our options as far as channel security if we are not using ftp ( and
is it possible in the first place across the internet).If we use a
secure ftp site, can the agents manage that?
2.Load: Our publisher has about 20 databases right now, with a
total of 1Gig file space occupied by mdf and log files. One database
is being replicated. Its consuming 1Gig of RAM Memory. Is that normal?
Is it because of the replication. How can I find out? Can anybody with
experience in this area, tell how much more load we can expect to
see? How much processing is needed for 40 users each updating about
500KB of data every one hour?
Thanks a lot,
Hananiel
1) I'm confused by what you are referring to by ftp. Are you talking about
the ftp port (21) or the ftp service. IE can the merge agent download the
commands using FTP? The answer is no, only the snapshot. If you are talking
about using port 21 the answer is yes. The merge agent will connect to the
publisher/distributor/subscriber using port 1433 or whatever port your SQL
Server is configured to run on, which could be port 21.
2) SQL Server will consume as much memory as is accessible on the machine or
whatever you configure SQL Server to consume using sp_configure 'max server
memory (MB)'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0409170710.68893ce9@.posting.google.c om...
> Hello,
> I am replicating databases from a sql2000 server with a
> seperate distributer running sql2000 server and a MSDE subscriber. I
> am using merge replication. The subscribers pull a subscription.
> We want to have this setup across the internet for multiple
> subscribers
> each of whom might be updating as frequently as 1 hour. There are a
> couple of issues I would like to find out about.
> 1.Security: I understood that the initial snapshots can be
> published via ftp ( or any other means ofcourse). Can the merge
> process be accomplished via ftp too? i.e The merge agent running on
> the subscriber, writes to the ftp space reserved for it and the
> publisher uses these files to bring the publisher up to speed and put
> the updates back to all the subscribers. (sounds very slow). What are
> our options as far as channel security if we are not using ftp ( and
> is it possible in the first place across the internet).If we use a
> secure ftp site, can the agents manage that?
> 2.Load: Our publisher has about 20 databases right now, with a
> total of 1Gig file space occupied by mdf and log files. One database
> is being replicated. Its consuming 1Gig of RAM Memory. Is that normal?
> Is it because of the replication. How can I find out? Can anybody with
> experience in this area, tell how much more load we can expect to
> see? How much processing is needed for 40 users each updating about
> 500KB of data every one hour?
> Thanks a lot,
> Hananiel
|||Hilary Thanks!,
Does SqlServer natively support encryption of
communication between its remote merge agents and itself? Or should we use a
tool like secure shell to make an encrypted connection?
Thanks,
Hananiel
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eXjhIAOnEHA.644@.tk2msftngp13.phx.gbl...
> 1) I'm confused by what you are referring to by ftp. Are you talking about
> the ftp port (21) or the ftp service. IE can the merge agent download the
> commands using FTP? The answer is no, only the snapshot. If you are
talking
> about using port 21 the answer is yes. The merge agent will connect to the
> publisher/distributor/subscriber using port 1433 or whatever port your SQL
> Server is configured to run on, which could be port 21.
> 2) SQL Server will consume as much memory as is accessible on the machine
or
> whatever you configure SQL Server to consume using sp_configure 'max
server
> memory (MB)'
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Hananiel" <hananiel@.yahoo.com> wrote in message
> news:e338e321.0409170710.68893ce9@.posting.google.c om...
>
Saturday, February 25, 2012
Replication Issues
Labels:
aseperate,
database,
databases,
distributer,
iam,
merge,
microsoft,
msde,
mysql,
oracle,
replicating,
replication,
running,
server,
sql,
sql2000,
subscriber
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment