balloning t-log

Every Satuday evening my t-log balloons and consume my available drive
space. What can I do to monitor the og so i can try to see what is
causing this to keep happening.
I have interrogated the application support ema to see if they do any
large amount of work that would cause the problem but only "not me"
answers
any help/suggestions are greatly appreciated.
Can you set up a trace to see who is doing what? My guess is something like
index rebuilds.
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:ecd7839d-fec3-4378-8502-ca2d1cfb11ce@.s12g2000prg.googlegroups.com...
> Every Satuday evening my t-log balloons and consume my available drive
> space. What can I do to monitor the og so i can try to see what is
> causing this to keep happening.
> I have interrogated the application support ema to see if they do any
> large amount of work that would cause the problem but only "not me"
> answers
> any help/suggestions are greatly appreciated.
|||On Jan 20, 7:41Xpm, "Kalen Delaney" <replies@.public_newsgroups.com>
wrote:
> Can you set up a trace to see who is doing what? My guess is something like
> index rebuilds.
> --
> HTH
> Kalen Delaney, SQL Server MVPwww.InsideSQLServer.comhttp://blog.kalendelaney.com
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:ecd7839d-fec3-4378-8502-ca2d1cfb11ce@.s12g2000prg.googlegroups.com...
>
>
>
> - Show quoted text -
I do perform maintenance at 1am on Sunday mornings which does an index
reorg but not a rebuild. would performing maintenance more often help
or will that balloon the logs suring the production week which I don't
want to happen.
Any suggestions are welcomed.
|||Also use the script from BOL that checks fragmentation first and only redoes
stuff that needs it. Also, if you avoid clustered indexes (unless severely
fragmented) that could keep logging down too.
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:OBPTWM9WIHA.1208@.TK2MSFTNGP03.phx.gbl...
> Yes, re-organising OR rebuilding databases does cause massive transaction
> logging.
> Instead of actually rebuilding or re-organising your indexes, you might be
> better off just rebuilding index statistics (which doesn't generate such
> massive log entries). You should also look into tuing the queries which
> are scanning your tables - these queries are the ones benefiting from the
> re-orgs / rebuilds but they'd probably run much better if they just had a
> good index.
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> Benchmark your query performance
> http://www.SQLBenchmarkPro.com
> "NC3" <ncoleman3@.yahoo.com> wrote in message
> news:f69cf48c-bdeb-4026-9bb0-bd01ae9627b5@.c23g2000hsa.googlegroups.com...
> On Jan 20, 7:41 pm, "Kalen Delaney" <replies@.public_newsgroups.com>
> wrote:
> I do perform maintenance at 1am on Sunday mornings which does an index
> reorg but not a rebuild. would performing maintenance more often help
> or will that balloon the logs suring the production week which I don't
> want to happen.
> Any suggestions are welcomed.
>