| Author |
Topic |
|
steel
Posting Yak Master
107 Posts |
 Posted - 2008-07-22 : 06:16:26
|
| hello all,I have configured log shipping on sql2005 server but facing issue regarding too much grown size of the t log as well as backupof the t log .please tell me shall i will be able to shrink the log file by creating a job that runs frequently ......thank u.................... |
|
|
sql_er
Constraint Violating Yak Guru
267 Posts |
Posted - 2008-07-22 : 09:51:30
|
| I don't know much about log shipping ... but can try to help:1. How often do you backup the transaction log?2. Do you have other jobs running on your system (how often): |
 |
|
|
sql_er
Constraint Violating Yak Guru
267 Posts |
Posted - 2008-07-22 : 09:52:11
|
| I don't know much about log shipping ... but can try to help:1. How often do you backup the transaction log?2. Do you have other jobs running on your system (how often):- Index Defragmentation- Rebuild Index- Optimization3. Do you have replication on your system? |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-22 : 09:53:36
|
| You should backup T log backup frequently . Can you shrink log file after you take t-log backup? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-22 : 22:44:27
|
| How big is the log file? How often do you backup log? Is the big log file on source server or on secondary ones? |
|
|
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2008-07-25 : 13:10:18
|
| I don't know about 2005 but in 2000, if there is an issue with the log shipping, the originating server's log will continue to grow until the log-shipping process completes successfully on the destination server. I had an instance where my log grew to 60GB because log shipping wasn't completing to the destination server. Looking at the originating server and the log jobs, all appeared to be running normal but once I went to the destination, I found there were issues.Terry |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-07-25 : 13:22:44
|
quote:
Originally posted by tosscrosby
I don't know about 2005 but in 2000, if there is an issue with the log shipping, the originating server's log will continue to grow until the log-shipping process completes successfully on the destination server. I had an instance where my log grew to 60GB because log shipping wasn't completing to the destination server. Looking at the originating server and the log jobs, all appeared to be running normal but once I went to the destination, I found there were issues.Terry
That isn't how log shipping works. Log shipping deals only with transaction log backups and does not read the source server's transaction log. It doesn't matter if the copy and/or the restore job is faililng, it does not impact the source server.If your log grew to 60GB (and not the tlog backup), then the issue wasn't with log shipping.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
steel
Posting Yak Master
107 Posts |
Posted - 2008-07-29 : 12:07:07
|
| hi all,the log shipping i know is working very much fine as i am using the secondary server for MIS purposes and everything is fine but the isuue is with very large transaction log backups ,,,,,,please tell me that am i able to shrink the transaction log of the database on the primary server frequently through a job or it wil break the log chain??????thank you. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
urgent t_log size very high in log shipping