Question about SqlServer Transaction Log File

Hey Guys,

My Sql Server transaction Log is now 1.4 Gig and my Database size is 1.o GIG.
Is this common or can I clean up the Transaction Log?

How can I go about cleaning the Log?
I am looking to boost the performance of Sql Server

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The transaction log will grow each time you make a transaction against the database, so if you don't put something in place to clean the transaction  log it will keep growing. It isn't a problem that it is larger than the database.

Don't expect much of a performance improvement from cleaning it - the sql server will continue to write to the log each time a transactino occurs,and this writing is what worsens performance (by a very small amount).

You can set a maximum size on the transaction log by right clicking the database and selecting properties, then navigating to the 'transaction log' tab. You can also set up a database maintenance plan to remove old transaction logs.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Aneesh RetnakaranDatabase AdministratorCommented:
>Is this common or can I clean up the Transaction Log?
Seems like you are not taking the backups of your transaction log, which is really very risky unless you have a job offer in your hand; So make sure that you takes the regular backups of your Log
Dont let your transaction log reach its maximum size ever as this will halt action on the db, scheulde a regular transaction log back up as this will truncate the log.

Alternatively set your db to Auto_shrink mode as this will keep it under control
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

sonu19Author Commented:
I got this error on the Log file backup

Microsoft (R) SQLMaint Utility (Unicode), Version [Microsoft SQL-DMO (ODBC SQLState: 08001)] Error 0: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
You shoudl be able to set the back up withinin ssms if you are using 2005? shoudlnt see this error?

Right click database select backup and then select transaction data log
sonu19Author Commented:
I dont see anything to select Transaction log all I see is the delete inactive activity from transaction log
i am on a sql server enterprise manager

tells you how to use dbcc shrinkfile to shrink your transaction log, however this wont back it up, in em you shoudl have back up transaction log within the back up window

sorry its been a while since i used 2k
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.