Home Forums SQL Server 2005 SQL Server 2005 Performance Tuning Costly update trigger -70,000,000 logical reads for 30,000 rows updated! RE: Costly update trigger -70,000,000 logical reads for 30,000 rows updated!

  • February 1, 2009 at 5:15 am

    #936137

    Thanks guys for your responses.

    I should clarify that this is not a one-off event.

    Whenever the trigger is executed, the number of reads is always in the millions, while the number of rows updated in the base table is typically in the 30,000-row ballpark.

    Looking at the execution plan has not raised any flags (in my mind).

    I'm thinking, maybe the query I use to capture the info is not correct? (see my previous posting right above)

    Perhaps I should run a server-side trace zeroing in on the trigger execution to get an independent confirmation on the number of reads.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]