Re: Trimming HUGE Transaction Log
- From: "Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 13 Oct 2008 19:10:57 +0200
Are you doing regular transaction log backups? If not, set the database in simple recovery model and keep it there.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Always OpenTo Suggestions" <AlwaysOpenToSuggestions@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:897A198B-D293-43A3-86A9-3FD18D9F5E62@xxxxxxxxxxxxxxxx
I've got an Access application with a SQL Server back end.
SQL Server db is about 4 gig. Transaction log is about 10 gig. It just
seems to keep growing. I' GUESSING Access never causes transactions to be
committed, so the log file never drops those transactions.
I tried something which SEEMS to work, but before I do this to production
files - I'd like a little expert advice.
-- I backed up the database
-- I changed the recovery model to SIMPLE,
-- I shurunk the log file to the minimum allowed (which was very small)
-- I changed the recovery model back to FULL.
If I do this after hours when everyone is gone, logging should begin before
users every get back into the office. Does this seem like a plan??
--
Thanx in advance!
Angelo
.
- Follow-Ups:
- Re: Trimming HUGE Transaction Log
- From: Always OpenTo Suggestions
- Re: Trimming HUGE Transaction Log
- References:
- Trimming HUGE Transaction Log
- From: Always OpenTo Suggestions
- Trimming HUGE Transaction Log
- Prev by Date: Trimming HUGE Transaction Log
- Next by Date: Re: Trimming HUGE Transaction Log
- Previous by thread: Trimming HUGE Transaction Log
- Next by thread: Re: Trimming HUGE Transaction Log
- Index(es):
Relevant Pages
|
