Basic questions ...

We are considering using replication for some of our needs and I need a few
basic questions answered so I can let my boss know what some of the gotcha's
are.
Using transactional replication, distributor and publisher on the same
serveer, read only subscribers:
1) What happens to the subscriber when you restore a database and/or
transaction logs on a publisher?
2) Can synchronization be forced outside of the normal scheduling? I.E. if
we sync nightly but the VP of marketing gets a bright idea and says I need
the lasted data, can we force synchronization ad hoc?
3) What happens with DDL on published objects?
4) What is the meaning of life?
5) Are there any rules of thumb about additonal load on the publisher's
database server? There is obviously some overhead for running the agents and
distibution database, but if you are replicating say 10% of the
transactions, is this analogous to adding yet an additonal 10% load on the
publisher's server?
6) We will be doing this over a VPN between separate domains. We are
expecting nightly synchronization to be required, but I was wondering if
more regular syncs would be more reliable over less than perfect internet
connections (DSL and cable are likely. Dial-up in worse cse scenarios). Any
thoughts?
Thanks,
Bob Castleman
DBA Poseur
Bob,
I will leave questions 1, 2, 3, 5 & 6 to the pros (HC & PI), but as far
as #4, I received an email a while back that said...
What is the meaning of life?
The meaning of life is to give and receive love and work at something
you feel passionate about. Or not.
I hope this helps.
Larry....
|||1) when you restore a publication db you basically break replication on the
publisher. Nothing happens to the subscriber
2) Sure. You can synchronize at any time or any time interval.
3) Making DDL changes on SQL 2000 and SQL 7 server is not allowed. You can
make some schema changes (DDL) using sp_repladdcolumn and sp_repldropcolumn.
In SQL 2005 most schema changes will be replicated.
4) life is nasty, solitary, brutish and short, however it is a hauntingly
beautiful universe. Time is all we really own. Value it carefully. Spend it
with someone special. Replicate often
5) Its typically between 5 and 10%, but it can vary wildly depending on what
you are replicating, hardware, replication type, throughput etc.
6) By replicating as frequently as possible you will lessen the load on your
publisher/distributor. The longer between sync's the greater the performance
degradation.
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
"Bob Castleman" <nomail@.here> wrote in message
news:%23oB45H3aFHA.1600@.tk2msftngp13.phx.gbl...
> We are considering using replication for some of our needs and I need a
few
> basic questions answered so I can let my boss know what some of the
gotcha's
> are.
> Using transactional replication, distributor and publisher on the same
> serveer, read only subscribers:
> 1) What happens to the subscriber when you restore a database and/or
> transaction logs on a publisher?
> 2) Can synchronization be forced outside of the normal scheduling? I.E. if
> we sync nightly but the VP of marketing gets a bright idea and says I need
> the lasted data, can we force synchronization ad hoc?
> 3) What happens with DDL on published objects?
> 4) What is the meaning of life?
> 5) Are there any rules of thumb about additonal load on the publisher's
> database server? There is obviously some overhead for running the agents
and
> distibution database, but if you are replicating say 10% of the
> transactions, is this analogous to adding yet an additonal 10% load on the
> publisher's server?
> 6) We will be doing this over a VPN between separate domains. We are
> expecting nightly synchronization to be required, but I was wondering if
> more regular syncs would be more reliable over less than perfect internet
> connections (DSL and cable are likely. Dial-up in worse cse scenarios).
Any
> thoughts?
>
> Thanks,
>
> Bob Castleman
> DBA Poseur
>
|||Thanks, guys.
My own answer to #4
The meaning of life is that we indeed are alive.
"Bob Castleman" <nomail@.here> wrote in message
news:%23oB45H3aFHA.1600@.tk2msftngp13.phx.gbl...
> We are considering using replication for some of our needs and I need a
> few basic questions answered so I can let my boss know what some of the
> gotcha's are.
> Using transactional replication, distributor and publisher on the same
> serveer, read only subscribers:
> 1) What happens to the subscriber when you restore a database and/or
> transaction logs on a publisher?
> 2) Can synchronization be forced outside of the normal scheduling? I.E. if
> we sync nightly but the VP of marketing gets a bright idea and says I need
> the lasted data, can we force synchronization ad hoc?
> 3) What happens with DDL on published objects?
> 4) What is the meaning of life?
> 5) Are there any rules of thumb about additonal load on the publisher's
> database server? There is obviously some overhead for running the agents
> and distibution database, but if you are replicating say 10% of the
> transactions, is this analogous to adding yet an additonal 10% load on the
> publisher's server?
> 6) We will be doing this over a VPN between separate domains. We are
> expecting nightly synchronization to be required, but I was wondering if
> more regular syncs would be more reliable over less than perfect internet
> connections (DSL and cable are likely. Dial-up in worse cse scenarios).
> Any thoughts?
>
> Thanks,
>
> Bob Castleman
> DBA Poseur
>