Also, when you truncate a transaction log, all this does is to remove
committed database transactions from that log.  It does not shrink the
physical size of the transaction log file.  That's where SHRINKFILE comes
in.

Here's a link to Microsoft's support site with more info
http://support.microsoft.com/kb/873235

Over a long course of time, if you are using Remedy with all the add-ons
you list, that transaction log can grow quite large.

Joseph Kasell
Network Management Integrator
Telecommunications Division
Navy Federal Credit Union
820 Follin Lane
Vienna, Virginia  22180
703/206-2007


                                                                           
             Kaiser Norm E CIV                                             
             USAF 96 CS/SCCE                                               
             <[EMAIL PROTECTED]                                          To 
             N.AF.MIL>                 arslist@ARSLIST.ORG                 
             Sent by: "Action                                           cc 
             Request System                                                
             discussion                                            Subject 
             list(ARSList)"            Re: Transaction log is full.        
             <[EMAIL PROTECTED]                                             
             ORG>                                                          
                                                                           
                                                                           
             07/12/2007 10:52                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
             [EMAIL PROTECTED]                                             
                    RG                                                     
                                                                           
                                                                           




This is a multi-part message in MIME format.

------_=_NextPart_001_01C7C494.39F6FAB3
Content-Type: text/plain;
             charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

If you don't have a good SQL maintenance plan in place, the transaction
log just grows and grows and grows over time.  The transaction log can
grow quite a bit if you run, say, an escalation or filter that modifies
1000s of records.  Then do that a few days a week, and in no time the
transaction log is huge.

=20

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of DJHuang
Sent: Thursday, July 12, 2007 9:49 AM
To: arslist@ARSLIST.ORG
Subject: Re: Transaction log is full.

=20

** Hi,

   Regarding to this transaction log full issue, it is not how you
truncate the transaction log file but how the transaction log file=20
   got full that interests me. We have a v7 ARS server with IM, PM, CM,
SLM, CMDB, EIE for SQL installed.=20
   After about 6 months running, we hit the same situation. There are
about 20000 incident tickets in the db and=20
  2000 contact information replicated/updated nightly. It end up with a
more than 100GB transaction log file. =20
   Does anyone know what kind of behavior would generate a log file so
large?
  Thank you.

DJHuang

2007/7/12, Broyles Robert K Mr CTR USAF 96 CS/SCCE <
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>:

Thanks Joe.  I went back and reread the SQL books online and say that my

syntax was wrong.  I didn't need to specify TRUNCATEONLY if I pass it a
file size.

Rob

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"


__20060125_______________________This posting was submitted with HTML in
it___=20


_______________________________________________________________________________

UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

------_=_NextPart_001_01C7C494.39F6FAB3
Content-Type: text/html;
             charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

**
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:*
{behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape
{behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
    {font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal,
li.MsoNormal, div.MsoNormal
   {margin:0in;
      margin-bottom:.0001pt;
font-size:12.0pt;
 font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
      text-decoration:underline;}
a:visited,
span.MsoHyperlinkFollowed
     {color:blue;
      text-decoration:underline;}
span.EmailStyle18
 {mso-style-type:personal-reply;
     font-family:Arial;
color:navy;}
@page Section1
    {size:8.5in 11.0in;
     margin:1.0in 1.25in
1.0in 1.25in;}
div.Section1
    {page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If you don&#8217;t have a good SQL
maintenance plan in place, the transaction log just grows and grows and =
grows
over time.&nbsp; The transaction log can grow quite a bit if you run, =
say, an
escalation or filter that modifies 1000s of records.&nbsp; Then do that =
a few days a
week, and in no time the transaction log is =
huge.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Action Request
System discussion list(ARSList) [mailto:<st1:PersonName =
w:st=3D"on">arslist@ARSLIST.ORG</st1:PersonName>]
<b><span style=3D'font-weight:bold'>On Behalf Of </span></b>DJHuang<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, July 12, =
2007 9:49
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">arslist@ARSLIST.ORG</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: Transaction =
log is
full.</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>** Hi,<br>
<br>
&nbsp;&nbsp; Regarding to this transaction log full issue, it is not how =
you
truncate the transaction log file but how the transaction log file <br>
&nbsp;&nbsp; got full that interests me. We have a v7 ARS server with =
IM, PM,
CM, SLM, CMDB, EIE for SQL installed. <br>
&nbsp;&nbsp; After about 6 months running, we hit the same situation. =
There are
about 20000 incident tickets in the db and <br>
&nbsp; 2000 contact information replicated/updated nightly. It end up =
with a
more than 100GB transaction log file.&nbsp; <br>
&nbsp;&nbsp; Does anyone know what kind of behavior would generate a log =
file
so large?<br>
&nbsp; Thank you.<br>
<br>
DJHuang<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><span class=3Dgmailquote><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>2007/7/12, <st1:PersonName =
w:st=3D"on">Broyles Robert K
 Mr CTR USAF 96 CS/SCCE</st1:PersonName> &lt;<a
href=3D"mailto:[EMAIL PROTECTED]" target=3D"_blank">
[EMAIL PROTECTED]</a>&gt;:</span></font></span><o:p></o:p><=
/p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Thanks Joe.&nbsp;&nbsp;I went back and reread the SQL books =
online and
say that my <br>
syntax was wrong.&nbsp;&nbsp;I didn't need to specify TRUNCATEONLY if I =
pass it
a<br>
file size.<br>
<br>
Rob<br>
<br>
_________________________________________________________________________=
______<br>
UNSUBSCRIBE or access ARSlist Archives at <a =
href=3D"http://www.arslist.org";
target=3D"_blank">www.arslist.org</a> ARSlist:&quot;Where the Answers =
Are&quot;<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
__20060125_______________________This posting was submitted with HTML in =
it___ <o:p></o:p></span></font></p>

</div>

</body>

</html>
__20060125_______________________This posting was submitted with HTML in
it___

------_=_NextPart_001_01C7C494.39F6FAB3--

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to