GEM News - Last Updated October 10 2006
The following is the latest GEM update news. While release specifics are contained in the Change Log, LatestNews.htm will give a broad understanding of what is being worked on and releases.Priority To Do / Outstanding Issues
The main priority TO DO item involves filming the tutorial so that you can see screenshots for the installation. This is a fairly large task - and i need to find the time to complete it.Completed In October 2006
New Scheduled Job: PurgeMSDBBackupHis
This win32 batch job will purge 30 days of sql server backup history per run. It will autoschedule itself to run weekly - allowing you to catch up over a period of time if you have a large msdb. Or you could just run the command multiple times...GetSybMDASqlText.pl
I got sick and tired of getting calls that system X is slow - knowing the application was at fault - but not being able to trace what was going on. The MDA tables are available - but the data fragmented into multiple talbes - not what i want to be deciphering at 3am... So i wrote ADMIN_SCRIPTS/bin/GetSybMDASqlText.pl which does a fetch of the 3 main dynamic/pipe MDA tables (monSysSQLText, monSysStatement, and monSysPlanText), stores the results in memory, and then prints a decent report on what has been going on for your server. The code will probably need to be updated with filters - because you probably only want to see slow queries, but am not sure how to approach filtering. Probably need to consider real time flushing of data... ie. printing stuff as it happens... but i would then need to figure out when the info is all ready... working on it... Output kind of looks like:DATA FOR SPID=52 KPID=774111325 BATCHID=8 SQL TEXT:exec Heartbeat_proc @monitor_program ='Win32Eventlog', @system ='SYS3', @subsystem ='ADSRV004', @state ='RUNNING' SUBKEY=ContextID/PlanID,DBID/ProcedureID SUBKEY ITEM Line 1 1:0:0:0 CpuTime 0 1:0:0:0 PhysicalReads 0 1:0:0:0 PagesModified 0 1:0:0:0 WaitTime 0 1:0:0:0 LogicalReads 0 1:0:0:0 PacketsReceived 0 1:0:0:0 PacketsSent 0 1:0:0:0 Elapsed Time 0 MonSysStatement: DBID=4 OBJECTID=709678645 IMPLIES OBJECTNAME=Heartbeat_proc SUBKEY ITEM Line 0 Line 15 Line 38 Line 42 Line 58 Line 59 1:8734:4:709678645 CpuTime 0 0 0 0 0 10 1:8734:4:709678645 PhysicalReads 0 0 0 0 0 0 1:8734:4:709678645 PagesModified 0 0 0 0 0 0 1:8734:4:709678645 WaitTime 0 0 0 0 0 0 1:8734:4:709678645 LogicalReads 0 0 0 3 0 4 1:8734:4:709678645 PacketsReceived 0 0 0 0 0 0 1:8734:4:709678645 PacketsSent 0 0 0 0 0 0 1:8734:4:709678645 Elapsed Time 0 0 0 0 0 10 SHOWPLAN KEYS = ContextID:PlanID:SequenceNumber SHOWPLAN [0:0:1] => QUERY PLAN FOR STATEMENT 1 (at line 1). SHOWPLAN [0:0:2] => STEP 1 SHOWPLAN [0:0:3] => The type of query is EXECUTE.The above case is kind of useless (who cares about the plan of an EXEC...) but i allready found one production problem with this monitor.
GEM Introduction Presentation
Complete GEM Documentation
