Hi Paul,

Here I quote from the IBM Technote:

SQL Server log truncation occurs at the completion of any BACKUP LOG statement. 
When using the DP for SQL to backup the logs, this would be performed by 
issuing the command:
tdpsqlc back DBName log /truncate=yes
The default for the "tdpsqlc backup ... log" command is for truncate=yes.

Best Regards,

Martin Panggabean | 
 
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Paul Dudley
Sent: Friday, January 23, 2009 10:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP Sql question about log growing

Can that log backup be run within TDP Sql or does it have to be run
using MSSQL?

Thanks & Regards
Paul

Paul Dudley
Senior IT Systems Administrator
ANL Container Line Pty Limited

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Del Hoobler
Sent: Friday, 23 January 2009 1:38 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP Sql question about log growing

Robert,

You need to run a LOG backup in order to truncate the logs.

BTW, truncating the transaction log does not reduce the size of a
physical log file; it reduces only the size of the logical log file.
To reduce the size of a physical log file, it is necessary to shrink the
file,
using, for example, the DBCC SHRINKFILE command.

Here is an IBM Technote that discusses it:
        http://www-01.ibm.com/support/docview.wss?uid=swg21199294
If you want real deep details, look here:
        http://msdn.microsoft.com/en-us/library/ms190440.aspx

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/22/2009
03:31:10 AM:
> TDP Sql question about log growing
>
> Robert Ouzen Ouzen
>
> to:
>
> ADSM-L
>
> 01/22/2009 03:32 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Hi to all
> In a sever Windows 2003 with  SQL database I saw that a log increase
> very much ( to +26 GB) , it was programmed  with the option Recovery
> Model:  Full
>
> I run every day a full backup (not any log backup) with the command:
>
> tdpsqlc backup * full /tsmoptfile=%sql_dir%\dsm.opt /logfile=%
> sql_dir%\sqlfull.log >> %sql_dir%\sqlsched.log
>
> I add those lines in my dsm.opt:
>
> INCLUDE "\...\meta\...\*"     mgwhighlearnf
> INCLUDE "\...\data\...\*"      mgwhighlearnf
>
> If I understand correctly the full backup truncate the log after it
> finish ??? In my case running just full backup I can turn it to just
> Recovery Model:  simple
>
> But just for knowledge why the full backup did not clear the log ?????
> I first turn the Recovery Model to: simple to run a shrinking
> procedure (turn the log to 10MB).
>
> By the way what the difference if instead of the lines of the
> INCLUDE I wrote previous I will write:
>
> INCLUDE "\...\meta\...\full*"     mgwhighlearnf
> INCLUDE "\...\data\...\full*"      mgwhighlearnf
> And let my recovery model to:  Full
>
> Did now it will truncate the log after each full backup ??????? or I
> need to add a truncate option somewhere ????
>
> My TDP for SQL version is 5.2.1.0
>
> Regards,
>
> Robert Ouzen





        
ANL DISCLAIMER

This e-mail and any file attached is confidential, and intended solely to the 
named addressees. Any unauthorised dissemination or use is strictly prohibited. 
If you received this e-mail in error, please immediately notify the sender by 
return e-mail from your system. Please do not copy, use or make reference to it 
for any purpose, or disclose its contents to any person.