Anonymous_User Absent Member.
Absent Member.
470 views

SQL_HungJobs KS


Andy,
Did you ever update this one? Or is there something else you would
recommend? I'm not seeing anything similar in the last SQL release. I
updated the SQL statement to work with 2012 but the script acts a bit
flaky. I can't ever get it to stop with out cold starting the agent.


--
swpyatt
------------------------------------------------------------------------
swpyatt's Profile: https://forums.netiq.com/member.php?userid=4240
View this thread: https://forums.netiq.com/showthread.php?t=53211

0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: SQL_HungJobs KS


No - I have not updated it. What did you feel you had to change for SQL
2012? Its working fine on SQL 2014. I suspect that it is using outdated
code in a cluster environment so needs changing for that reason, but the
SQL side is fine


--
Andy Doran
Software Engineer Consultant (NetIQ)
------------------------------------------------------------------------
andy_doran's Profile: https://forums.netiq.com/member.php?userid=3937
View this thread: https://forums.netiq.com/showthread.php?t=53211

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SQL_HungJobs KS


That was all I did, hack together the cluster code. I did not modify the
query (thought I did after all that cluster code.)


--
swpyatt
------------------------------------------------------------------------
swpyatt's Profile: https://forums.netiq.com/member.php?userid=4240
View this thread: https://forums.netiq.com/showthread.php?t=53211

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SQL_HungJobs KS


I have now updated the KS... I made a change to another KS recently to
change how it determines the cluster information using WMI instead of
the old MSCluster COM object, so I plugged that into SQL_HungJobs. Seems
to be working fine for me on a cluster (Windows 2012/SQL 2014). Note
that we have a new "SQL Server" module which has the cluster code in the
module rather than in KS code. The current release of that does not
allow for ad-hoc queries, but there is a patch for it which does. When
that goes on "general release" i may update this KS to be a SQLServer KS
instead of a SQL KS and that removes the need for any KS code to
determine virtual server on-line status.

Attaching the updated KS


+----------------------------------------------------------------------+
|Filename: SQL_HungJobs.zip |
|Download: https://forums.netiq.com/attachment.php?attachmentid=277 |
+----------------------------------------------------------------------+

--
Andy Doran
Software Engineer Consultant (NetIQ)
------------------------------------------------------------------------
andy_doran's Profile: https://forums.netiq.com/member.php?userid=3937
View this thread: https://forums.netiq.com/showthread.php?t=53211

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.