July 15, 2005 at 2:47 am
Hi
In my experience the size of a tran log directly corresponds with the amount of data written. So a large log means large amounts of data written. (an index defrag is a logged operation!)
Do you notice this each day? Are you running any index defrag jobs or some other daily maint routines? Are there any users creating copies of large tables?
JP
July 15, 2005 at 5:35 am
Hi JP de Jong
Thanks for the answer, but:
-NO large amounts of data are written.
(this changes even occurs when no user is connected)
-I do not make any index defrag.
-Each day I notice this.
-NO users are creating copies of large tables
-There are NO other daily maint routines.
-Except for one done at 1:00 DB Optimization.
Also, Auto Stats are Off.
I hope it helps in founding the reason my log is so changing.
Thanks in advance
July 15, 2005 at 5:38 am
There must be some kind of process writing data I guess. If you cretae a sql profiler trace we you can maybe find out what's going on.
JP
July 15, 2005 at 1:38 pm
Hi JP
I have cretae a sql profiler trace, but nothing appears to populate the database so big, in order to increase the log size.
Looking a the log size (the big one) with notepad I See lots of blanks in it.
I don't know what else to do.
The log changes in size from one moment to another, and there is no pattern to follow.
Any Ideas?
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply