Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.replication:70959
hello all,
I have implemented a transactional replication (queued updating) that
creates a full replica of the main database. The size of the main db is 15GB
and the replicated db's size is 12GB. I would like to know why this
difference.
thank you,
peti
Peti,
a few questions:
are you replicating the complete database?
Are you comparing the actual size after taking account of shrinking etc?
Are the indexes contiguous?
Do you have exactly the same set of indexes?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thank you Paul,
Sorry for delay.
I have some answers for your questions:
The complete database is replicated and I shrunk all dbs before to compare.
I have the same set of indexes that are fragmented, I supose, because they
were never rebuilt.
Cheers,
peti
"Paul Ibison" wrote:
> Peti,
> a few questions:
> are you replicating the complete database?
> Are you comparing the actual size after taking account of shrinking etc?
> Are the indexes contiguous?
> Do you have exactly the same set of indexes?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Wednesday, March 21, 2012
database size
Labels:
database,
gbl,
implemented,
microsoft,
mysql,
oracle,
phx,
public,
queued,
replication,
replication70959hello,
server,
size,
sql,
sqlserver,
tk2msftngp08,
transactional,
updating,
xref
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment