 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Replication / January 2006Initial syncronization problem
Hi, Transactional log on the subscriber is growing so fast that is running of disk space. I can't truncate and shrink it. What can be done in this situation? put it in full recover model, dump the tlog, then shrink it to something smaller, and put it in bulk copy mode.  SignatureHilary 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 > Hi, > Transactional log on the subscriber is growing so fast that is running of > disk space. I can't truncate and shrink it. What can be done in this > situation? Recovery model is simple, do I really need to change it to full? TLog should be truncated. > put it in full recover model, dump the tlog, then shrink it to something > smaller, and put it in bulk copy mode. > > Hi, > > Transactional log on the subscriber is growing so fast that is running of > > disk space. I can't truncate and shrink it. What can be done in this > > situation? Unfortunately even in recovery model full, I can't free space - log is active, all pages are in use. > Recovery model is simple, do I really need to change it to full? > TLog should be truncated. [quoted text clipped - 5 lines] > > > disk space. I can't truncate and shrink it. What can be done in this > > > situation? Did you dump it? SignatureHilary 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 > Unfortunately even in recovery model full, I can't free space > - log is active, all pages are in use. [quoted text clipped - 10 lines] >> > > disk space. I can't truncate and shrink it. What can be done in this >> > > situation? I got following: 1. no free space left on disk because transaction log size. It became 114 GB. 2. replication agent rollbacked transactions 3. only after it stopped the work I could truncate and shrink the log 4. changed recovery model from simple to bulk logged 5. I started distribution agent again but got the same picture. It seems that the log will occupy all 200 GB. I do not have space on disk necessary to finish initial syncronization. What can I do in this situation? Can I avoid such growth of the log? Database is 160 GB. It is heavy used almost all the time. I do not have opportunity to get downtime. > Did you dump it? > [quoted text clipped - 12 lines] > >> > > disk space. I can't truncate and shrink it. What can be done in this > >> > > situation? this database is likely too large to synchronize via the snapshot. Can you restore a copy of it on the source server, truncate any tables you don't need, and make sure all identity columns, triggers, and constraints are not for replication. SignatureHilary 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 >I got following: > 1. no free space left on disk because transaction log size. It became 114 [quoted text clipped - 28 lines] >> >> > > this >> >> > > situation? I know that I need to disable triggers on subscriber. I have no identity columns. But do I need to delete constraints (FK) on the subscriber? > this database is likely too large to synchronize via the snapshot. Can you > restore a copy of it on the source server, truncate any tables you don't [quoted text clipped - 33 lines] > >> >> > > this > >> >> > > situation? No, you don't need to - just make sure they are marked not for replication. After you have done this do a no sync subscription. Make sure that no DML is going on on your publisher between the time you have done your backup and applied it. SignatureHilary 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 >I know that I need to disable triggers on subscriber. I have no identity > columns. But do I need to delete constraints (FK) on the subscriber? [quoted text clipped - 41 lines] >> >> >> > > this >> >> >> > > situation? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.