Re: [sap-basis] Reduce size of transaction log
Posted by
Admin at
Share this post:
|
0 Comments
Posted by Sadiq (SAP BASIS Consultant) on Mar 30 at 1:43 AM | Mark as helpful |
Hi.
i doing weekly full backup daily differential backup and hourly transaction
log backup.
with 130GB of data. from SQL Mgt studio.
its working fine.
On Mon, Mar 29, 2010 at 7:00 PM, carl.kepford via sap-basis <
sap-basis@groups.ittoolbox.com> wrote:
> Posted by carl.kepford
> on Mar 29 at 9:32 AM
> Hi David,
>
> I don't think it should be a normal thing to do this on a regular basis.
>
> I wouldn't want to give advice to anybody about backups without an in depth
> analysis of their business needs, DB size, and hardware setup. But, if the
> business can stand a day's loss of data in DEV and QAS, it might be better
> to change the SQL backup method to SIMPLE nd skip transaction log backups
> altogether. Do Full backups every night. Or Full backups weekly and
> differential nightly.
>
> If business requirements can't take a day's loss of data in QAS and DEV,
> then stay with the SQL setting at FULL and do transaction log backups often
> enough so that this situation comes up only in very unusual cases.
>
> Again, very dangerous to give advice without knowing anything about their
> business requirements and hardware capacity relevant to DB size. I'm only
> throwing out these as examples.
>
> ---------------Original Message---------------
> From: deepakpandey
> Sent: Wednesday, March 17, 2010 6:34 AM
> Subject: Reduce size of transaction log
>
> > Hi all,
> >
> > I just want to truncate transaction logs. plz tell me whether in
> truncating process how we reduce size of t-log .
> > bcoz i m new to do this.
> > Also tell differance b/w truncation & shrink.
> > I am using here Microsoft SQL 2005 Databaes with SAP ECC 6.0.
> >
> > Thanks,
> > Deepak ...
__.____._ i doing weekly full backup daily differential backup and hourly transaction
log backup.
with 130GB of data. from SQL Mgt studio.
its working fine.
On Mon, Mar 29, 2010 at 7:00 PM, carl.kepford via sap-basis <
sap-basis@groups.ittoolbox.com> wrote:
> Posted by carl.kepford
> on Mar 29 at 9:32 AM
> Hi David,
>
> I don't think it should be a normal thing to do this on a regular basis.
>
> I wouldn't want to give advice to anybody about backups without an in depth
> analysis of their business needs, DB size, and hardware setup. But, if the
> business can stand a day's loss of data in DEV and QAS, it might be better
> to change the SQL backup method to SIMPLE nd skip transaction log backups
> altogether. Do Full backups every night. Or Full backups weekly and
> differential nightly.
>
> If business requirements can't take a day's loss of data in QAS and DEV,
> then stay with the SQL setting at FULL and do transaction log backups often
> enough so that this situation comes up only in very unusual cases.
>
> Again, very dangerous to give advice without knowing anything about their
> business requirements and hardware capacity relevant to DB size. I'm only
> throwing out these as examples.
>
> ---------------Original Message---------------
> From: deepakpandey
> Sent: Wednesday, March 17, 2010 6:34 AM
> Subject: Reduce size of transaction log
>
> > Hi all,
> >
> > I just want to truncate transaction logs. plz tell me whether in
> truncating process how we reduce size of t-log .
> > bcoz i m new to do this.
> > Also tell differance b/w truncation & shrink.
> > I am using here Microsoft SQL 2005 Databaes with SAP ECC 6.0.
> >
> > Thanks,
> > Deepak ...
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
In the Spotlight
_.____.__ White Papers
In the Spotlight
55% of IT Pros Use Social Media to Advance Their Careers. See the Survey Results