sql server replication: I have a SQL 2000 enterprise database that is roughly 400GB. I am trying =
to setup transactional replication. During the publication and =
initialization of the database the tempdb on the SQL server publishing =
the database grows very large and I run out of disk space. I let it grow =
to 70GB then had to cancel the process because I was out of disk space. =
Is this normal?=20
Is there a way to work around this problem if it is normal other then =
buying more disk space.


--=20

The problem is I need a second copy of the database to always =
up-to-date. Doing a backup method would not work because the data will =
quickly become out of data after it has been restored to the secondary =
server.

--=20
Christopher Tatro
Central Standard Time
tatroc@email.uophx.edu
[quoted text, click to view]
With databases this large you really need to consider another way of =
deploying your subscriber. I would look at using a backup with a no-sync =
subscription.

--=20
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
=20


[quoted text, click to view]
I have a SQL 2000 enterprise database that is roughly 400GB. I am =
trying to setup transactional replication. During the publication and =
initialization of the database the tempdb on the SQL server publishing =
the database grows very large and I run out of disk space. I let it grow =
to 70GB then had to cancel the process because I was out of disk space. =
Is this normal?=20
Is there a way to work around this problem if it is normal other =
then buying more disk space.


--=20

Is anyone else here trying to replicate a SQL 2000 database which is =
comparable to 400GB in size?




--=20
Christopher Tatro
Central Standard Time
tatroc@email.uophx.edu
[quoted text, click to view]
I have a SQL 2000 enterprise database that is roughly 400GB. I am =
trying to setup transactional replication. During the publication and =
initialization of the database the tempdb on the SQL server publishing =
the database grows very large and I run out of disk space. I let it grow =
to 70GB then had to cancel the process because I was out of disk space. =
Is this normal?=20
Is there a way to work around this problem if it is normal other then =
buying more disk space.


--=20

With databases this large you really need to consider another way of =
deploying your subscriber. I would look at using a backup with a no-sync =
subscription.

--=20
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
=20


[quoted text, click to view]
I have a SQL 2000 enterprise database that is roughly 400GB. I am =
trying to setup transactional replication. During the publication and =
initialization of the database the tempdb on the SQL server publishing =
the database grows very large and I run out of disk space. I let it grow =
to 70GB then had to cancel the process because I was out of disk space. =
Is this normal?=20
Is there a way to work around this problem if it is normal other then =
buying more disk space.


--=20

Hilary already gave you the solution.
Instead of normal SNAPSHOT generation which would take up a consider =
amount of time and disk space, define your as no-sync subscription.

Kuen
[quoted text, click to view]
The problem is I need a second copy of the database to always =
up-to-date. Doing a backup method would not work because the data will =
quickly become out of data after it has been restored to the secondary =
server.

--=20
Christopher Tatro
Central Standard Time
tatroc@email.uophx.edu
[quoted text, click to view]
With databases this large you really need to consider another way of =
deploying your subscriber. I would look at using a backup with a no-sync =
subscription.

--=20
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
=20


[quoted text, click to view]
I have a SQL 2000 enterprise database that is roughly 400GB. I am =
trying to setup transactional replication. During the publication and =
initialization of the database the tempdb on the SQL server publishing =
the database grows very large and I run out of disk space. I let it grow =
to 70GB then had to cancel the process because I was out of disk space. =
Is this normal?=20
Is there a way to work around this problem if it is normal other =
then buying more disk space.


--=20