Post reply

Query Usage

  • April 12, 2010 at 5:01 am

    #143926

    Hi Team,

    We have a production server. Application is running adhoc queries on the database which causing the unexpected growth of log file of that database.

    Now what we need to check is which query is causing that much growth of the log file.

    SQL Server version is 2005, SP3 and 4266.

    Can any body help me in this.

    Thanks in advance.

    Thank You.

    Regards,
    Raghavender Chavva

  • April 12, 2010 at 5:36 am

    #1149935

    Idera has a really great tool for tracking this stuff. Its called Diagnostic Manager:

    http://www.idera.com/Products/SQL-Server/SQL-diagnostic-manager/

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • April 12, 2010 at 6:11 am

    #1149956

    Schadenfreude-Mei (4/12/2010)

    Idera has a really great tool for tracking this stuff. Its called Diagnostic Manager:

    http://www.idera.com/Products/SQL-Server/SQL-diagnostic-manager/%5B/quote%5D

    Will SQLDM shows, which query is using how much log space in that database ?

    We have installed Idera SQLDM 6.0 already in our environment and we are monitoring our instances from that tool only.

    Can you please let me know how to check the my requirment in SQLDM ?

    Thank You.

    Regards,
    Raghavender Chavva

  • April 12, 2010 at 6:26 am

    #1149968

    Track down in Resources when the log grew (using point-in-time) and then using the point-in-time, go to sessions and look at what was running.

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • April 12, 2010 at 6:40 am

    #1149978

    Ok, we can track the queries...but here can we track which query is using most database log space ?

    Thank You.

    Regards,
    Raghavender Chavva

  • April 12, 2010 at 6:55 am

    #1149998

    Well you would look at what queries are going on while or just before the log grows and then you would just have to analys those queries (there cant be that many).

    Just look at the top 5 for cpu and memory usage and odds-on it will be one of those.

    Adam Zacks-------------------------------------------Be Nice, Or Leave

  • April 12, 2010 at 9:19 am

    #1150120

    You could omit select queries since they don't cause log growth.

    Do you have ETL processes that are importing or updating large amounts of data ?

  • April 12, 2010 at 10:19 am

    #1150159

    No...It dont have any ETL operations...

    Thank You.

    Regards,
    Raghavender Chavva

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply