• hurricaneDBA - Thursday, April 27, 2017 1:58 PM

    You know I remember that the application support guy is running reorganization and index maintenance jobs I'll check the jobs tomorrow me see what he is running but my guess is this could be the reason for the logs being so full. This is our production server and the space capacity for logs I think are 10GB so I can't use more than that unless I ask for more space. I'll set the TL to 5GB to test it first then I'll see if I can get more space from the systems team Thanks for the query I'll run it tomorrow also and let you know KY

    Heh... you should also try to convince your application support guy that "running reorganization and index maintenance jobs" is largely a waste of time.  Please see any article in the following Google search by any of Brent Ozar's group.  I thought he was drinking bong water through 2 straws but tried it to prove them wrong and they're not wrong.  I haven't done index maintenance on my production box since 17 Jan 2016 (more than a year now) and performance actually got noticeably better over the first 3 months.  The important thing is to rebuild stats.
    https://www.google.com/#q=Should+I+worry+about+index+fragmentation

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)