<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=387012812-31012007><FONT face=Arial
color=#0000ff size=2>There are a couple of things here. First you need to ensure
the records are being pruned, have you changed the max numbers of records
allowed from the default of 1.2million, DBL service parameter? Is CAR installed
& configured to remove CDR & ART records after a set number of days? If
the answer to all of the above is yes you may have an issues with the
transaction log not being cleared. You cab check the transaction in SQL
Enterprise Manager by changing the view to Status View, it will be in the
left window graphically. Keep in mind that once the total allocated space
is expanded it will never shrink in size by it's self. Also regular
backups of the Pub will truncate & purge automatically.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=387012812-31012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=387012812-31012007><FONT face=Arial
color=#0000ff size=2>To purge the transaction log & shrink the DB manually
in SQL query analyzer, may or may not need the "'s depending on the SQL
version:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=387012812-31012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2>
<TABLE cellSpacing=1 cellPadding=2 width=600 border=0>
<TBODY>
<TR>
<TD background=../images/inactive-ffffff.gif><PRE>Here is how we truncated the transaction log for CDR:
1) ISQLW
2) select the CDR DB
3) execute "dump tran "<SPAN class=387012812-31012007>CDR</SPAN>" with no_log"</PRE></TD></TR>
<TR>
<TD background=../images/inactive-ffffff.gif><PRE>Had to truncate the <SPAN class=387012812-31012007>ART</SPAN> transaction log through ISQLW<SPAN class=387012812-31012007>:</SPAN>
1) ISQLW
2) select the <SPAN class=387012812-31012007>ART</SPAN> DB
3) execute "dump tran "<SPAN class=387012812-31012007>ART</SPAN>" with no_log"
</PRE><PRE><SPAN class=387012812-31012007>Mike</SPAN></PRE></TD></TR></TBODY></TABLE></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Ruben Montes
(Europe)<BR><B>Sent:</B> Wednesday, January 31, 2007 3:54 AM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> [cisco-voip] CDR_log.LDF huge
size<BR></FONT><BR></DIV>
<DIV></DIV>
<P>Hi,</P>
<P>I have noticed that my CDR_log.LDF file, that is located in C:\Program
Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and is growing 5GB per
week. I suppose there should be a bug behind, but the for the moment I want to
stop this growing... </P>
<P>Do you know if it is enough with putting the service parameter CDR Enabled
flag to false to stop collecting CDR information? Later on I'll see how we will
purge this because I assume it will be a CPU intensive process...</P>
<P>I have a TAC case opened, but for the moment the engineer it is not helping
me very much...</P>
<P>Regards,</P>
<P>Ruben</P></BODY></HTML>