Welcome to dbFreaks.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Planning for Transactional Replication (Size and Speed)

  
   Database Help (Home) -> Replication RSS
Next:  Wildcard for Enter Parameter Value Box?  
Author Message
JDS

External


Since: Feb 04, 2008
Posts: 12



(Msg. 1) Posted: Wed Dec 17, 2008 7:25 am
Post subject: Planning for Transactional Replication (Size and Speed)
Archived from groups: microsoft>public>sqlserver>replication (more info?)
We are in the process of implementing transactional replication. We will be
using a remote distributor. Our environment is SQL Server 2005 64 bit on
Windows server 2003 Enterprise edition. I need to know if there is a
standard way of sizing and optimizing the distribution. We have ample space
on our subdisk but I want to give our SAN guy some particulars regarding
space. Is the size of the distribution database contingent on the number of
articles and changes or is the size pretty static? What the best way to
configure the size from the start? Also we have 10k and 15k drives available
from a speed perspective. I'd like to place the disrtibution database on the
slighty slower drives even possibly slower than 10k. Does anyone see any
issues with that?

 >> Stay informed about: Planning for Transactional Replication (Size and Speed) 
Back to top
Login to vote
Hilary Cotter

External


Since: Jan 16, 2008
Posts: 143



(Msg. 2) Posted: Wed Dec 17, 2008 8:50 am
Post subject: RE: Planning for Transactional Replication (Size and Speed) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Given a fixed budget I would invest in RAM over disks.

10k should be find for the speed, but I'd run disk speed/throughput tests to
see what your bottleneck currently is and what sort of throughput you are
currently getting.

Distribution database size is a function of how many commands, what sort of
commands, and what your retention is. Replicating text or wide tables will
consume more space, than narrow tables.

Also your disk cleanup task may not work efficiently which may increase the
size of the distribution database. This been said, I think the smallest
commercially available SCSI drives are 73 Gigs, so with a 4 drive RAID 10
configuration would you have 146 Gigs, 4 drive RAID 5 should be 219 Gigs.

Both sizes should be ample for most high throughput distribution databases.

"JDS" wrote:

> We are in the process of implementing transactional replication. We will be
> using a remote distributor. Our environment is SQL Server 2005 64 bit on
> Windows server 2003 Enterprise edition. I need to know if there is a
> standard way of sizing and optimizing the distribution. We have ample space
> on our subdisk but I want to give our SAN guy some particulars regarding
> space. Is the size of the distribution database contingent on the number of
> articles and changes or is the size pretty static? What the best way to
> configure the size from the start? Also we have 10k and 15k drives available
> from a speed perspective. I'd like to place the disrtibution database on the
> slighty slower drives even possibly slower than 10k. Does anyone see any
> issues with that?

 >> Stay informed about: Planning for Transactional Replication (Size and Speed) 
Back to top
Login to vote
sql_noob

External


Since: Dec 12, 2008
Posts: 9



(Msg. 3) Posted: Thu Dec 18, 2008 9:46 am
Post subject: Re: Planning for Transactional Replication (Size and Speed) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
On Dec 17, 11:50 am, Hilary Cotter wrote:
> Given a fixed budget I would invest in RAM over disks.
>
> 10k should be find for the speed, but I'd run disk speed/throughput tests to
> see what your bottleneck currently is and what sort of throughput you are
> currently getting.
>
> Distribution database size is a function of how many commands, what sort of
> commands, and what your retention is. Replicating text or wide tables will
> consume more space, than narrow tables.
>
> Also your disk cleanup task may not work efficiently which may increase the
> size of the distribution database. This been said, I think the smallest
> commercially available SCSI drives are 73 Gigs, so with a 4 drive RAID 10
> configuration would you have 146 Gigs, 4 drive RAID 5 should be 219 Gigs.
>
> Both sizes should be ample for most high throughput distribution databases.
>
>
>
> "JDS" wrote:
> > We are in the process of implementing transactional replication.  We will be
> > using a remote distributor.  Our environment is SQL Server 2005 64 bit on
> > Windows server 2003 Enterprise edition.  I need to know if there is a
> > standard way of sizing and optimizing the distribution.  We have ample space
> > on our subdisk but I want to give our SAN guy some particulars regarding
> > space.  Is the size of the distribution database contingent on the number of
> > articles and changes or is the size pretty static?  What the best way to
> > configure the size from the start?  Also we have 10k and 15k drives available
> > from a speed perspective.  I'd like to place the disrtibution database on the
> > slighty slower drives even possibly slower than 10k.  Does anyone see any
> > issues with that?- Hide quoted text -
>
> - Show quoted text -

data and log i think we are at 50GB or so for the ditribution db. this
is for several databases that are close to 1TB combined size, around
50 total publications, 100 or so subs and millions of transactions
replicated daily. a few times a month we run large jobs that hit 50-70
million commands.
 >> Stay informed about: Planning for Transactional Replication (Size and Speed) 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Combining Transactional Replication and Merge Replication - I would like to know if this scenario is possible: I have main database (Server A) that I replicate to another server using transactional replication (Server B), know I would like to publish this database on Server B as a merge publication and then...

Transactional Replication - I had 3 servers 2 transactional servers and one is main server i.e., Multiple Publishers and Single Subscriber A(TRANS SERVER) B(TRANS SERVER) C(MAIN SERVER) I HAD CONFIGURED TRANSACTION REPLICATION A TO C AND B TO C In these servers i had taken on...

Can you have transactional replication of blobs? - I am having an issue using transactional replication on a SQL 2005 SP2 system when trying to replicate an Image data type. The data won't write to the Prod system, let alone replicate. However, when I remove the table from the publication everything..

Bidirectional Transactional replication - Hi All Do any one know where to get good Knowledge resources for writing and implementing stored procedures for bidirectional transactional replication. I f any body has one implemented recently can you spare the steps involved and the best practises....

UDFs & Transactional Replication - I created a UDF... create FUNCTION dbo.WhatLocationIsThis() RETURNS numeric AS begin declare @return as numeric SELECT @return = Location FROM storemain..tblLocationTable return @return end GO When I run 'select dbo.WhatLocationIsThis()' it..
   Database Help (Home) -> Replication All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]