And if that’s not enough, developers on other platforms ridicule us iSeries developers about our archaic development tools, and when they are not ridiculing us they speak in condescending tones about our “legacy” applications. Now they want GUI-based business applications, too. After all, the user community is getting more accustomed to GUI-based applications everyday, in the form of e-mail and the Microsoft Office Suite of products. You can create a monitor for this purpose with the Create Row Count Diff Monitor operation, available in the right-click menu for the grid.Such envy is understandable. In addition to tracking the number of rows in a table over time, you may want to see by how many rows the value changes. Setting it to 0 or a negative number tells DbVisualizer to always clear the grid between executions of monitors. You can change the value to limit or extend the number of rows that DbVisualizer should keep. This property is initially set to 100 when you use Create Row Count Monitor to create the monitor. You define the maximum number of rows in the Max Row Count field in the details area at the bottom of the Scripts tab. SELECT '$$' AS PollTime,ĭbVisualizer keeps the result for previous executions, up to the specified maximum number of rows, so that you can see how the result changes over time. When the maximum row limit is reached, the oldest row is removed when a new row is added. Every time the monitor is executed, a new row is added to the grid, up to a specified maximum number of rows. It creates a monitor with SQL for returning a single row with the timestamp for when the monitor was executed and the total number of rows in the table at that time. The right-click menu in the grid for a table or result set therefore has a Create Row Count Monitor operation that creates a monitored statement for you automatically. It is very common to want to keep track of how the number of rows in a table varies over time. The following sections describe how you can get help creating the bookmarks for a couple of cases that are commonly used for monitoring.
#DBVISUALIZER NOT LIKE HOW TO#
For information about how to manually create, manage and share monitored statements, please see the Managing Frequently Used SQL page. The main difference is how they are used and a couple of additional ways monitored statements can be created. You can create and work with monitored statements in the same way as with a Bookmark. The Year and MonthNum are there just to get the correct ascending order of the result. The interesting columns in the result are the Month and Count. The following is an example of the result set produced by the statement: The figure above shows the Incidents/Day monitored statement and the SQL that is associated with it. If you don't want to see these details, you can disable it with the Show Details toggle control in the right-click menu for a node. This information is displayed, and can be edited, in the lower part of the Scripts tab, along with information about the file that holds the monitored statement. It also has a title, a maximum row count (how many results to keep track of) and a visibility status (whether the monitored statement result should be included in the Monitors windows, discussed below). A monitored SQL statement is associated with information about the target database connection and (optionally) the catalog (the JDBC term which translates to a database for some databases, like Sybase, MySQL, SQL Server, etc) and schema.