Post reply

Good Practice for monitoring a table

  • April 19, 2012 at 7:49 am

    #267734

    A table from a 3rd party app (on 2008R2) needs to be monitored constantly to avoid user impact. To accomplish this, I've been using a SQL Agent job (running on a different server) every minute to fire a quick SSIS package that checks for problems in the table (i.e. records have been active for too long), and if it finds them, puts the problem rows into an html email and sends it to the support team.

    It's been up and working for a while now, but I keep getting the feeling that this is one of those "when all you have is a hammer..." moments. Is there a better tool to use for this need?

  • April 19, 2012 at 9:20 am

    #1476084

    That sounds like a perfectly valid method to me. There are certainly other tools such as Powershell or VBScript that can be used but as long as what you're doing is working I don't think there's any reason to switch.

Viewing 2 posts - 1 through 1 (of 1 total)

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