-----Original Message-----
From: Anthon, Mark J - DOA
Sent: Thursday, September 28, 2006 11:35 AM
To: 'John A DAVIS '
Subject: RE: kinda quick solution needed to truncate transaction log
Yes, you are correct; often we would manually put a database into simple
mode prior to updating stats or reindexing to avoid the glut of
resulting tran_logs, and then switch back to full mode later. What we
finally did to help eliminate the whole issue, was to incorporate the
two steps I mentioned into a nightly backup job.
Some databases, the real heavy hitters (OLTP) which require point in
time recovery, also require hourly tran-log back-ups. And even in that
case, one can add those two steps to manage the tran log size. Really,
I guess the bottom line always seems to be space and storage. Yes,
performance can occasionally be adversely effected by having a huge
tran_log as well, but space seems to be the larger issue.
Incorporating these two steps into database backups and/or tran log
backups ("as final steps") has saved us much pain; give it a try.
-----Original Message-----
From: John A DAVIS [mailto:John.A.[Email address protected]
Sent: Thursday, September 28, 2006 11:02 AM
To: Anthon, Mark J - DOA
Subject: RE: kinda quick solution needed to truncate transaction log
**A LazyDBA.com subscriber has responded to your lazydba.com post**
**LazyDBA.com mail shield has forwarded you this email, **and removed
any attachments, and kept your email address secret **from this person,
and any viruses/trojans.
**If you reply to this email, the person will see your email address as
normal **Anything below this line is the original email text
what about update stats? doesn't that play in here somewhere? and if so,
is it time intensive?
>>> "Anthon Mark J - DOA "
[Email address protected] 9/28/2006 8:46 AM >>>
I will continue to share whatever knowledge I have, whenever I can.
In
fact, in anticipation of the next tran-log inquiry, here's the two step
process once again, for those of you new to the group or those of you
who have not yet mastered the highly complex "cut & paste" technique,
which takes years to perfect:
To put out the immediate fire (the band aid approach):
Step One: BACKUP LOG database_name WITH TRUNCATE_ONLY
Step Two: dbcc shrinkfile (log_name,truncateonly)
-----Original Message-----
From: Mordechai Danielov
[mailto:mssqldba-ezmlmshield-x78439759.[Email address protected]
Sent: Thursday, September 28, 2006 10:15 AM
To: LazyDBA Discussion
Subject: RE: kinda quick solution needed to truncate transaction log
That depends on where you are. In the land of down under it already is
Friday. :)
-----Original Message-----
From: Edwards Ed
[mailto:mssqldba-ezmlmshield-x30987813.[Email address protected]
Sent: Thursday, September 28, 2006 11:10 AM
To: LazyDBA Discussion
Subject: RE: kinda quick solution needed to truncate transaction log
Phew! Oh my! Temperrrrrrrr! Don't worry! Be happy! It's almost
Fridayyyyy! Partyyyyyyy! Hehe.
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
MS Sql Server LazyDBA home page