Re: Transaction logs getting too large
From: Keith Kratochvil (sqlguy.back2u_at_comcast.net)
Date: 05/18/04
- Next message: Brian Moran: "Re: Obsolete technology - dblibrary"
- Previous message: Tibor Karaszi: "Re: Transaction logs getting too large"
- In reply to: srgallan: "Transaction logs getting too large"
- Next in thread: Charles T. Blankenship, MDSD: "Re: Transaction logs getting too large"
- Reply: Charles T. Blankenship, MDSD: "Re: Transaction logs getting too large"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 07:23:48 -0500
If you don't care about transaction logs you can set the recovery model to simple
ALTER DATABASE YourDatabase SET RECOVERY SIMPLE
You will probably need to shrink the log file after setting the recovery model to simple. Refer to DBCC SHRINKFILE within Books Online (within the SQL Server program group).
-- Keith "srgallan" <anonymous@discussions.microsoft.com> wrote in message news:e8ec01c43cd0$a10fae00$a501280a@phx.gbl... > Hello everyone, > > I was hoping to get a little guidance if someone has a > chance. We have SQL2000 here for applications that > require it's services in the back-end. One paticular > application "we will call application A" has a very small > database but an 80GB transaction log file. > > This is not a critical database, this application is just > used by the IT department for file deployments. > > Transaction logs are used for recovery correct? Can we > set it so that older information in the logs are purged? > Truncate the log and delete older one's?
- Next message: Brian Moran: "Re: Obsolete technology - dblibrary"
- Previous message: Tibor Karaszi: "Re: Transaction logs getting too large"
- In reply to: srgallan: "Transaction logs getting too large"
- Next in thread: Charles T. Blankenship, MDSD: "Re: Transaction logs getting too large"
- Reply: Charles T. Blankenship, MDSD: "Re: Transaction logs getting too large"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|