Showing posts with label built. Show all posts
Showing posts with label built. Show all posts

Wednesday, March 21, 2012

Monitoring the running and execution of SSIS packages with MOM

Hi,

Has anyone monitored the execution of SSIS packages with MOM? Are there extreme benefits over just utilizing the built in execution and event logs, as well as the Windows Event Viewer?

What is the recommended way to monitor SSIS execution?

Thanks,

- Joel

Joel,

I have a very very limited knwoledge of MOM... However you can log many things to the event log with SSIS (job execution with SQL Agent, logging to event log, ...). I'm not aware of anything "standard" for SSIS & MOM...

|||

They're not quite there yet with MOM integration. We had a similar project to integrate into Tivoli and the way I got around it was to use logging providers to output into the Windows Event Log. Tivoli had hooks into the Event Log for the events I gave it and whalla....pagers blaring. If your concern is more from the operations perpective, you may have better luck using the SQL Server log provider and creating operations reports for your production support. You can use these and events like the OnPipelineRowsSent to trap "hung" packages or tasks.

Sorry there's not a better answer but direct MOM integration is just a matter of time.

-- Brian

sql

Friday, March 9, 2012

Monitoring agent status

All -
I'm trying to setup a way to monitor the agent status for replication. I
tried using the built in "Alerts" and they are not working. I made sure that
they are enabled, but after enabling the Alerts, it does not show that the
event had ever happened when I check the history. I've made sure that the
alerts are enabled on the distributor and no where else.
So my next question would be is there a way programatically monitor agents?
I see the system view sys.dm_qn_subscriptions, but when I select * from it,
nothing is returned.
I am trying to monitor the failures and retries.
"Paul Ibison" wrote:

> Which event re you monitoring. I recall from another poster that we couldn't
> get the on success alert running as the event couldn't get raised to the
> windows log (couldn't change the message attributes, unlike in SQL 2000) ,
> but I am not aware of any others.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
|||This should be ok. Are you using SQL 2000 or 2005? I'd l'll take a look later
on, but for now as a stop-gap you could use a notification on the job itself.
Cheers,
Paul
|||We are using 2005. I'll try and give the notification on the specific job a
try and see if that works.
"Paul Ibison" wrote:

> This should be ok. Are you using SQL 2000 or 2005? I'd l'll take a look later
> on, but for now as a stop-gap you could use a notification on the job itself.
> Cheers,
> Paul
>