Re: Transaction Log Size
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 11/24/04
- Next message: Wayne Snyder: "Re: Disk capacity and CPU/memory utilisation question?"
- Previous message: Mike London: "Re: ROW Limit and pages"
- In reply to: Steven Hutchinson: "Re: Transaction Log Size"
- Next in thread: Mark Allison: "Re: Transaction Log Size"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Nov 2004 13:33:22 +0100
Backup database does not empty the transaction log files. Backup log does. That is, however, not the
same thing as reducing the files size. Generally, you don't want to shrink the file size, let SQL
server have the size of the files it needs. I have some words about the topic as well as some links
to help you shrink the files at: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Steven Hutchinson" <it1@taysidefire.gov.uk> wrote in message news:%23$O6bCi0EHA.3976@TK2MSFTNGP09.phx.gbl... > Thanks for all your replies. > > We currently use a 3rd party backup agent to backup our SQL databases and > transaction logs (Commvault Galaxy iDataAgent for SQL) and the database is > in Full Recovery mode. It appears that the transaction logs are not reducing > in size after these regular backups are taking place. > > Because we are using a 3rd party agent to backup the database, do I still > need to issue the BACKUP LOG command before using DBCC SHRINKFILE? > > Should I get in touch with Commvault to query this or is this normal > behaviour if you use a 3rd party backup agent instead of the native sql > backup? > > > "John Bandettini" <JohnBandettini@discussions.microsoft.com> wrote in > message news:DC5C5FA6-1ED9-4CDA-9640-E3F5FA90A0EF@microsoft.com... > > Steven > > > > here are some articles on how to shrink your transaction log. > > > > INF: How to Shrink the SQL Server 7.0 Transaction Log > > http://support.microsoft.com/default.aspx?scid=kb;en-us;256650 > > > > INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE > > http://support.microsoft.com/default.aspx?scid=kb;en-us;272318 > > > > http://www.mssqlserver.com/faq/logs-shrinklog.asp > > > > I would guess that you have your database/databases in Full recovery mode > > and you have not been performing Transaction log backups. > > > > You need to either set them to simple recovery mode or schedule regular > > transaction log backups. > > > > To check the recovery mode of your databases, right click on the database > > in > > Enterprise Manager and choose options. You can chnage the mode from the > > window that will open. > > > > To perform transaction log backups (and database ones) you can use a > > wizard > > to set them up or you can create jobs manually and use the backup command. > > (See BOL for format) > > > > Hope this helps > > > > John > > > > "Steven Hutchinson" wrote: > > > >> Is it possible to reduce the size of the transaction log for a specific > >> database. At the moment one of our databases has a database of size of > >> 16Gb > >> and a transaction log of 43Gb!! > >> > >> As you might guess I am new to SQL Server but this doesn't seem right? > >> > >> Any help would be greatly appreciated.. > >> > >> > >> > >
- Next message: Wayne Snyder: "Re: Disk capacity and CPU/memory utilisation question?"
- Previous message: Mike London: "Re: ROW Limit and pages"
- In reply to: Steven Hutchinson: "Re: Transaction Log Size"
- Next in thread: Mark Allison: "Re: Transaction Log Size"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
