1

Topic: Sending SNMP traps by errors

Good afternoon, all!
Never such was, and here again...!
The maintenance department requested, that MS SQL 2014 and 2016 - sent to them SNMP Traps, by errors of operation Jobs and another. Sendings on MS Docs with  that MS stopped support SNMP with SQL 2005 - success did not crown. Gangways it submit...
What variants to manage with small losses? Itself I see the following:
1. To write powershell scripts which job check in the end its status and send SNMP.
2.???
I will be grateful for ideas.

2

Re: Sending SNMP traps by errors

Ferdipux;
In mailing snmp-trap the server should be engaged explicitly not.
As the variant can be swung SharpSnmpLib  unsafe assembly and to suppose the server to try to send directly from the server. (Never tried but in the theory can fly up)
Basically your vision for the decision of the task is worse nothing than usage of other indirect applications for mailing.
Most easier affairs are at Net-snmp.
And at PS for operation with the given protocol were  in delivery netcmdlets (I am a pity had not time to snatch when it free of charge distributed)

3

Re: Sending SNMP traps by errors

Ferdipux wrote:

What variants to manage with small losses? Itself I see the following:
1. To write powershell scripts which job check in the end its status and send SNMP.
2.???

2. To write  which checks presence of errors in  and sends SNMP

4

Re: Sending SNMP traps by errors

Ferdipux
https://msdn.microsoft.com/en-us/library/ms179428 (v=SQL.90).aspx

wrote:

a SQL Server 2005. A SQL Server no longer supports SNMP.