Comments
-
I believe (quick google research) that #AM_GET_QUERYSTATS is used by the SSMS Activity Monitor - someone has left Activity Monitor open in their session at a guess. sp_who2 should show you who is running it, and the host name.
-
No API that I am aware of, however this post from earlier in the year suggests SW are working on a scripted option. No timeframe for it, unfortunately. Re: Is it possible to script registering/unregistering a DB for monitoring and updating a DB instance name ?
-
You can set up a custom alert such as "Custom SQL Alert - Multiple Numeric Return" using something like this: SELECT JOBS.NAME AS [Job Name] ,DATEDIFF(minute, MAX(msdb.DBO.AGENT_DATETIME(RUN_DATE, RUN_TIME)), getdate() ) FROM msdb.dbo.SYSJOBS JOBS LEFT OUTER JOIN msdb.dbo.SYSJOBHISTORY JH ON JOBS.job_id = JH.job_id WHERE…
-
You might want to vote up this request, perhaps add your suggestions in the comments: Similar:
-
Just checking you've done all the post-fixpack steps? Assuming linux - db2iupdt instance, db2updv10 -d dbname, and rebinds? Might be worth verifying the monitor switches haven't changed after the FP install and restart (e.g. DFT_MON_STMT, DFT_MON_UOW etc). Yeah, I know it shouldn't happen, but maybe there was a deferred…
-
VM is fine - we run DPA on VM's (one for the App, one for the DB repository) monitoring 13 servers or so at the moment (a mixture of DB2 and SQL Server). No problems with it at all.
-
Just did a quick check - for 13 monitored instances I'm currently using ~26gb. Have you changed the default values for number of days of data history such as CLEAN_DAYS_OF_DETAIL etc? Otherwise you may need to open a ticket with support to investigate it. Edit - are you using SQL server as the repository? Is the space…
-
How would you decide on new input? Rows inserted? Rows updated? Rows deleted? What happens if they delete a row then add a row? How would you compare the difference? You could set up a custom alert to return table name and a row count or a boolean (true/false) or something similar, but I'm not sure that would really…
-
Port 1433 is the default SQL Server port. Is the port allowed via the firewall rules? Can you connect to the SQLEXPRESS instance directly on the server, or via SQL Server Management Studio from a workstation? Are there any error messages in the SQL log or the Windows Event log to indicate a problem? (SQL Error log default…
-
One thing I've noted before is the sparseness of the DPA documentation. Oh it's adequate for the installation and getting started, but it's very lacking in technical information. It's reasonably intuitive to get going, but definitely could use a bit more techy info for us techy DBA types There's a lot of info in the KB…
-
Either multiple executions of the query as Jim said, or there may be parallel query processing happening. It would be worth looking at the Historical Charts for the query and see how many executions there are, and what the main wait times are actually waiting on - there could be a tuning opportunity for you
-
jstafki wrote: Regarding software version, I cannot even determine which version we have - how do I do this? And then how to I get that handy looking Deadlocks tab to show up on my trends page? Thank you kindly, in advance! The version number will be shown on the logon screen (bottom, right hand side of the panel), or if…
-
Only indirectly using an email to SMS gateway, or as mandevil suggests use an SNMP trap. We have an email rule that looks for a specific keyword in the subject and then sends the email on to the gateway if the keyword is detected. Not pretty, but it works.
-
For DB2 9.7 and upwards, you can use "call monreport.LOCKWAIT" which will show who is holding and who is waiting on locks. Far easier than deciphering snapshots. There is also the Administrative view SYSIBMADM.MON_LOCKWAITS if you want to write your own queries/alerts. Related to this, you may want to look at the DB CFG…
-
You might need to raise this with support given the lack of responses here unfortunately. It may also be worth looking through the DPA logs first to see if there are any other clues buried there (on the DPA server under iwc/tomcat/logs directory).
-
If you only have DPA, there doesn't seem any advantage in going to 9.2. If you use the Orion tools, then it may be of use. Is DPA 9.2 of any value over 9.1 for non-Orion users?
-
Interesting link, thanks neomatrix1217 I suspect there will be "fun" times trying to port existing MSSQL databases to Linux. It's not clear if all features will be available in Linux either. I doubt the various GUI's will be there in their current forms (thinking SSMS, SSAS, SSRS etc) but I'd imagine/hope the client tools…
-
Have you checked that the username/password on that server is still valid? I had a similar problem when the password expired on one of our servers. Updated to "never expires" and reset the password and monitor started fine.
-
* You are shrinking their Empire - they control sharepoint, but not the new system. * You should have 'sold' it to their management first so that they mandate the new software, not you. (Shift the blame) * For any new software, there is a learning curve, which leads to - * There is always resistance to change - human…
