After replication, database size increased 4 times

Hi there,

Actually subject says every thing. Our database was 20GB in size and after
setting up replication its size is 73GB (with log).

Transaction Log's size is 10GB and 99% of it is empty and this is not a
concern because I can handle this by shrinking it.

However what am I gonna do with this 63GB data file? Only 3% of it is
unallocated and the rest of it is full of data but why? I mean, every table
has its Primary Key so Transactional Replication isn't supposed to add an
additional column to make some column in the tables unique right?

Is there any logical explanation of this increase?

Details:
54% Index
42% Data
3.5% Unallocated
0.10% Unused
Total Space Usage: 73.356MB
Data Files: 62.856MB
Log File: 10.500MB

Thanks for any tip
Joe

Wrong finding guys, the reason of this increase was setting up a Reindexing
maintenance plan with 20% fill factor. It has nothing to do with Replication.
Sorry for wasting your time.

"Joe" wrote:

> Hi there,
>
> Actually subject says every thing. Our database was 20GB in size and after
> setting up replication its size is 73GB (with log).
>
> Transaction Log's size is 10GB and 99% of it is empty and this is not a
> concern because I can handle this by shrinking it.
>
> However what am I gonna do with this 63GB data file? Only 3% of it is
> unallocated and the rest of it is full of data but why? I mean, every table
> has its Primary Key so Transactional Replication isn't supposed to add an
> additional column to make some column in the tables unique right?
>
> Is there any logical explanation of this increase?
>
> Details:
> 54% Index
> 42% Data
> 3.5% Unallocated
> 0.10% Unused
> Total Space Usage: 73.356MB
> Data Files: 62.856MB
> Log File: 10.500MB
>
> Thanks for any tip
> Joe