Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
vusil
Starting Member
22 Posts |
 Posted - 2005-09-07 : 03:54:25
|
| Hi guys,I'm having a problem with the templog growing to a massive size - from 400MB to 30G - when the snapshot replication runs. I end up running out of disk space and the replication fails with error "process could not bulk copy out of table '[dbo].syncobj_0X...]'".The default settings of tempdb have not been changed.Is this truly the cause of the replication failing?I'm using SQL server 2000 Enterprise Edition on NT, SP4Thank you. |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-09-07 : 04:58:22
|
| how large or a database are you replicating. How big is this table?Can you put your tempdb on a different disk with more space?-ec |
 |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-09-07 : 05:02:02
|
| Is this your initial snapshot? You could always take the copy yourself.-------Moo. :) |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-09-08 : 02:26:53
|
from a maintenance point of view, you need to purge that table(s), retain only active records and archive 'historical' ones if there are any and if you're replicating the entire database, i suggest you use logshipping or backup and restore procedures  HTH--------------------keeping it simple... |
|
|
|
|
|
|
Replication filling up templog