Post reply

iSpy (on your development)

  • June 3, 2013 at 8:40 pm

    #273490

    Comments posted to this topic are about the item iSpy (on your development)

  • June 19, 2013 at 3:35 pm

    #1625674

    If you end up with some excessive table growth.

    eg. Replication may be updating statistic regularly, rapid table drop & creates they can be excluded by adding

    if (condition)

    begin

    rollback

    end

    to the end of the Notifications_a_i trigger

  • June 19, 2013 at 11:10 pm

    #1625705

    Thanks for sharing. I have a similar monitoring in place using event notification but it's much simpler than yours. I only monitor changes to functions, stored procedures for selected databases (purely because of the requirements). Event notification is just awesome.

  • June 20, 2013 at 5:29 pm

    #1626166

    Patrick Ge (6/19/2013)

    Thanks for sharing. I have a similar monitoring in place using event notification but it's much simpler than yours. I only monitor changes to functions, stored procedures for selected databases (purely because of the requirements). Event notification is just awesome.

    Thanks, I started with a limited set - then it became difficult to manage with all the 'cases' of what data to capture. So a generic 'just-the-facts' system seemed in order.

    Event Notification is great - for procedures (you mentioned) I include the "Trace" events and track when each procedure is loaded into/ unloaded from the cache - Lets me track in-use, last used, details about procedures (Over time I should get an indication of the legacy junk that has accumulated)

  • May 2, 2016 at 12:56 pm

    #1875997

    Thanks for the script.

Viewing 5 posts - 1 through 4 (of 4 total)

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