• ScottPletcher (9/28/2016)


    Eric M Russell (9/28/2016)


    ScottPletcher (9/28/2016)


    You'd still need to keep at least the history from the previous check, because an index/table could be dropped, which would remove it from the system views.

    Aggregating object level statistics is problematic, but I'm thinking that comparing the delta of total bytes written for the database will work.

    True. Then again, the whole thing is rather problematic. I mean, I have code to check the differential bit maps that SQL itself uses for diff backups, but I only use it to rule out a diff backup if too many changes have been made, not to control whether a backup is done at all or not.

    Nice touch.

    I agree though. This is a bit of a sketchy solution to something that generally isn't a problem.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning