Re: Log Shipping....

Tech-Archive recommends: Speed Up your PC by fixing your registry

Just wondering, In log shipping environment, the log will auto shrink or
never shrink?


"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:upSAYxgfHHA.4704@xxxxxxxxxxxxxxxxxxxxxxx
I have no idea what environment you have. Is it the log backups that are
140GB in size of the transaction log itself? If it is the transaction log
file then you most likely have one of two conditions. Either you did not
start with a valid FULL backup or you have an open transaction that is
preventing the log from truncating. What does DBCC OPENTRAN() show for
that db?

--
Andrew J. Kelly SQL MVP

"Rogers" <naissani@xxxxxxxxxxx> wrote in message
news:%23XfwtzdfHHA.3648@xxxxxxxxxxxxxxxxxxxxxxx
There is a log shipping environment and I can't change any thing, if you
can let me know if change the intervel time from 15 to 20 mins, will that
helpful ?

Thanks

"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:OZPoY9SfHHA.4872@xxxxxxxxxxxxxxxxxxxxxxx
What are you doing? Are you backing up tot he same log file (device)
each time? If so stop that:). Backup to a different file each time by
adding a timestamp to the file name. Then the backups should be
relatively small and you can delete them after a specified time period.

--
Andrew J. Kelly SQL MVP

"Rogers" <naissani@xxxxxxxxxxx> wrote in message
news:%23nibvnRfHHA.1456@xxxxxxxxxxxxxxxxxxxxxxx
Log Shipping....

In my organization we had implemented Disaster Recovery (Log Shipping)
but Log File size is increasing gradually (140 GB) and Data File size
is 20 GB, I am just wondering log file size should be trancate once it
will ship to destination Server,

FYI, log ship every after 15 mins.

I would appreciate if any one can guide me how log could be shrink
automatically.

Thanks









.

Relevant Pages

  • Re: HELP!! Transaction Log is huge
    ... But the physcal file will not get shrink ... To avoid this after the transaction log backup you could do a DBCC ... SHRINKFILE on the LDF file frequently ...
    (microsoft.public.sqlserver.server)
  • Excesive Space Allocated
    ... Do a backup of the DB. ... Then shrink the file on the server (not local or it takes ... transaction log is allocated for around 2.5 gigs and I ...
    (microsoft.public.sqlserver.server)
  • Re: Transaction Log ENORMOUS!! Help
    ... If you are going to leave it in simple recovery, then you can shrink the ... Yesterday I changed backup model to SIMPLE from FULL. ... I realized the recovery model was set to FULL by our vendor, ... Transaction log is set to "automatically grow". ...
    (microsoft.public.sqlserver.server)
  • Re: ReportIoError 2 - any ideas?
    ... backup of transaction log and shrink the .ldf. ... >> striping is hardware based on all available drives - see ...
    (microsoft.public.sqlserver.server)
  • Re: Shrink transaction log after truncate table?
    ... What about the "Auto Shrink" option for a sql server database, would that be good, or just a waste resources? ... > I'm looking for a good way to shrink/compress this transaction log after I ... we also have our own custom log shipping process ...
    (microsoft.public.sqlserver.programming)