|
History of FB TraceManager |
|
|
|
|
History of FB TraceManager |
|
|
History of FB TraceManager
|
History of FB TraceManager |
|
|
|
|
History of FB TraceManager |
|
|
October 26, 2020 - v3.7.0.14
Enhancements:
| • | Update to Firebird Embedded V2.5.9 (#0001781) |
| • | Improve Firebird client-library handling in per-database area (#0001821) |
| • | Support for "log_warnings" trace configuration parameter (#0001822) |
| • | Support for "log_initfini" trace configuration parameter (#0001823) |
| • | Trace data/parser: Full support for init/new transaction id information in RETAINING scenarios (#0001827) |
| • | Experimental Firebird 4 Beta Support (#0001826) |
Bug fixes:
| • | Bug fixed: Database Statistics failing with recent Firebird 3.0 versions. (#0001714) |
| • | Bug fixed: Failed initial connect to server and database not handled correctly / silently ignored (#0001824) |
| • | Bug fixed: Parsed database statistics not shown in grids in specific situations (#0001825) |
April 27, 2016 - v3.6.0.11
Enhancements:
| • | Hotspots Analysis: Add configurable and optional auto refresh in hotspots area (#0001308) |
| • | Hotspots Analysis: Limit number of distinct textual info items to 500 (#0001374) |
| • | Firebird 3 support for 64-bit STATEMENT_ID, ATTACHMENT_ID and TRANSACTION_ID (#0001368) |
| • | Firebird 3 support for MON$SEC_DATABASE in monitoring table (#0001369) |
| • | Update to Firebird Embedded V2.5.5 (#0001373) |
Bug fixes:
| • | Bug fixed: Registering a server or database with a long password fails. (#0001359) |
| • | Bug fixed: ERROR AT event type should set event state to 1 (failed) instead of 0 (success). (#0001372) |
October 17, 2015 - v3.5.4.9
Enhancements:0001359: Registering a server or database with a long password fails
| • | Improve automatic purge handling for raw and parsed rows. (#0001234). - Raw max lines: Decreased new default to 50000 - Parsed max rows: Decreased new default to 10000 - Removed parsed purge rows setting. When the max setting is reached, all lines/rows are purged. This is more efficient. |
| • | Add button in project wizard to optimize session options for high throughput (Trial or Enterprise Edition only). (#0001297) |
| • | Updated Firebird Embedded to V2.5.4. (#0001285) |
Bug fixes:
| • | Bug fixed: Enhanced error diagnosis capabilities are disabled in release builds. (#0001233) |
| • | Bug fixed: Minor memory leaks in different areas. (#0001298) |
| • | Bug fixed: Random AV when right-clicking grid footer in database monitoring (database statistics, monitoring tables). (#0001299) |
October 10, 2014 - v3.5.3.10
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: Object Type in PSQL Call Stack monitoring table is not decoded properly for (stored) functions in Firebird 3. (#0001079) |
| • | Bug fixed: Firebird 3: MON$ table data for "Context Variables" is not fetched. (#0001080) |
| • | Bug fixed: Firebird 3: MON$ table data for "Memory Usage" is not fetched. (#0001081) |
October 9, 2014 - v3.5.3.7
Enhancements:
| • | Add support for additional Firebird 3 Beta 1 ODS 12.0 monitoring tables additions. (#0001068) |
| • | Make provided monitoring tables and grid columns aware of the connected database ODS. (#0001074) |
| • | Restore "Font size" setting for Raw trace data area upon trace session startup. (#0001075) |
Bug fixes:
| • | Bug fixed: First program startup for new installations may fail with an database error while upgrading metadata. (#0001073) |
| • | Bug fixed: Column header text may overwrite previous column text. (#0001063) |
| • | Bug fixed: Open Analysis cube may fail when executing for analysis entries with different SQL statements. (#0001076) |
September 30, 2014 - v3.5.2.10
Enhancements:
| • | Enhance UI docking capabilities across the entire product. (#0001038) |
| • | Update deployed Firebird embedded to V2.5.3. (#0001039) |
| • | Support for Firebird 3 "explain_plan" trace configuration option. (#0001040) |
| • | Allow per server Trace UI layout restoring regarding splitter positions. (#0001051) |
Bug fixes:
| • | Bug fixed: Form layout in Trace UI is sometimes screwed up upon connecting to the server. (#0001040) |
April 7, 2014 - v3.5.1.8
Enhancements:
| • | Purging of trace data: Support for purging of stored data in "Browse" module. (#0000871) |
| • | "About" menu item on the left in the main form to show the splash screen. (#0000870) |
Bug fixes:
| • | Bug fixed: Random AV when double-clicking in parsed trace data grid. (#0000864) |
| • | Bug fixed: "Go To Raw Line" navigation in parsed trace data grid jumps to wrong raw line. (#0000865) |
| • | Bug fixed: Random AV when deleting a project. (#0000872) |
February 25, 2014 - v3.5.0.18
Enhancements:
Random AV when double-clicking in parsed trace data grid
| • | Firebird 3 (Alpha 2) Support - Support in Header Page monitoring. (#0000799) - Support in Monitoring Tables integration. (#0000800) - Support in Database Statistics integration. (#0000802) - Stored function support in Trace API integration. (#0000830) - Package name support in parsed and persisted trace data. (#0000823) - Made package name in Procedure Hotspot part of the aggregation key. (#0000829) - Procedure Hotspot now also includes support for Firebird 3 stored functions. (#0000831) |
| • | Performance Improvements. (#0000816) - Execution time for adding parsed trace data rows has been decreased by up to 50%. This is especially noticeable in higher load environments. - Trace data fetching throughput when log to database is enabled has been improved by up to 250%. Writing parsed trace into the FBTM database is now completely asynchronously decoupled from the trace data fetcher thread. Trace data is now persisted in a fixed periodic interval of 10 seconds. |
| • | Improve usability/visibility in case with general trace session problems, e.g. when trace session can't be started, if it failed although started, if it is suspended due to log full situations. (#0000796) Added the following new "virtual" (no real event names from trace data) trace events: - TRACE SESSION ABORTED - TRACE SESSION FAILED - TRACE SESSION SUSPENDED |
| • | Allow more RAM being addressed although being a 32-bit application. On Windows 32-bit up-to 3GB and up-to 4GB on Windows 64-bit. (#0000835) |
| • | Add data-aware RawOutput tab/memo in Browse/Parsed area. (#0000797) |
| • | Add "Move To First" / "Move To Last" buttons in Visible Column Dialog. (#0000809) |
| • | Add trigger operation (delete, insert, update ...) and event type (before, after) into the trigger hotspot aggregation key to fully support Universal Triggers. (#0000814) |
| • | Update deployed Firebird Embedded version to 2.5.2 Update 1. (#0000815) |
| • | Configurable trace project-based option for maximum trace events per GUI refresh interval. (#0000818) |
| • | Enhanced statistics information for an active trace session. (#0000819) |
Bug fixes:
| • | Bug fixed: Clearing rows in Hotspots Analysis doesn't clear underlaying in-memory aggregated data. (#0000748) |
| • | Bug fixed: Selecting a system trace configuration template in Project Wizard should not overwrite the database name filter. (#0000798) |
| • | Bug fixed: Minor glitch in trace data parser parsing OPERATION for Database/DDL Triggers. (#0000810) |
| • | Bug fixed: Minor glitch in trace data parser parsing Remote Protocol for Non-Remote e.g. Embedded connections. (#0000811) |
| • | Bug fixed: Race condition when committing while parsed trace data is persisted. (#0000832) |
| • | Bug fixed: Stopping the FBTMLoggerSvc Windows Service could fail with an invalid pointer operation according to Windows Event Viewer. (#0000833) |
October 25, 2013 - v3.0.2.11
Enhancements:
| • | Expose and persist a "Has Garbage Collection" flag in parsed trace data based on the values in Detailed Statistics. (#0000740) |
| • | Expose and persist Garbage Collection total counters for Backout, Purge, Expunge in parsed trace data. (#0000741) |
| • | Expose and persist a "Has Garbage Collection" flag in Record Statistics tab in Monitoring Tables integration. (#0000742) |
Bug fixes:
| • | None |
March 19, 2013 - v3.0.1.61
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: Noticeable performance degradation in raw output after a first purge cycle. #0000588 |
| • | Bug fixed: Code Folding in raw output doesn't work. #0000589 |
March 15, 2013 - v3.0.0.58
Enhancements:
| • | Upgrade included Firebird Embedded Engine to V2.5.2. #0000489 |
| • | Support for parsed Detailed Statistics in trace data. #0000514 |
| • | Support for parsed sweep transaction counters in trace data. #0000516 |
| • | Visualize percentage columns in various data grids with an additional progress/percentage bar. #0000517 |
| • | Database Statistics: Add percentage of table and index size related to database size. #0000524 - Percentage of table size related to the database size - Percentage of index size related to total index size of database - Percentage of index size related to total index size per table |
| • | Add ability to view parsed trace column data in a separate modal dialog. Available in the parsed trace data grid context menu. #0000525 |
| • | Support for parsed Bind Variables in trace data. #0000527 |
| • | On-The-Fly "Statement Hotspot" view per active trace session added. The "Statement Hotspot" is an aggregated view on executed SQLs with various useful measures/counters (e.g. Execution Count vs. Prepare Count, number of distinct transactions per SQL, number of distinct execution plans per SQL and a lot more). Data is aggregated on-the-fly (incrementally) while the EXECUTE_STATEMENT_FINISH event is captured. Make sure to include the following trace configuration options, to fully take advantage of this new feature: log_statement_prepare, log_statement_free, log_statement_start, log_statement_finish. #0000540 |
| • | Re-arrange Registered Projects and Trace Session List areas to the upper client area. #0000541 |
| • | Database Statistics: Make index statistics detection dependent on a configurable number of nodes. Default value: 10000. #0000542 |
| • | Add SEVERITY information/column in Header Page and Database Statistics Monitoring. This will help to spot potential problems in header page and table/index statistics more quickly. #0000543 |
| • | Database Statistics: Make table statistics detection dependent on a configurable number of records. Default value: 10000. #0000544 |
| • | Parser throughput has been improved considerably. #0000563 |
| • | Visualization throughput has been improved considerably. #0000567 |
| • | "Paused" / "Dismissed when paused" option per visualization is now a global setting per trace tab. #0000568 |
| • | Add "Skipped Events" in Statistics tab of a trace session tab. This counts the number of skipped events in case of the Dismiss when paused option. #0000569 |
| • | Custom Trace Configuration Template storage. This allows to define templates/presets of trace configurations for later re-use in the Project Wizard. #0000571 |
| • | Disabled Trace Vizualisation mode, which results in a very light-weight trace processing with Hotspots data only. #0000572 |
| • | Removed Chart Trace Visualization as it doesn't provide any additional value. More useful charting to be expected in forthcoming releases. #0000573 |
| • | Support for Firebird Embedded as Traceable Server. #0000585 |
Bug fixes:
| • | Bug fixed: Charting in active trace session isn't purged like parsed trace data, thus prevents FBTM from running 24x7. #0000491 |
| • | Bug fixed: Random AV when closing an established database connection tab. #0000495 |
| • | Bug fixed: Random AV when closing an established server attachment tab. #0000496 |
| • | Bug fixed: Minor memory leak in internal structures in the per-database monitoring area. #0000515 |
| • | Bug fixed: Apply index statistics problem detection on live index metadata columns doesn't make sense when loading from file. #0000545 |
| • | Bug fixed: AV when loading header page gstat output only from file in Database Statistics. #0000547 |
| • | Bug fixed: Database Statistics: Minor glitch that Index Management is enabled where it shouldn't. #0000548 |
| • | Bug fixed: Random AV and/or lockups when closing a trace session tab while it's in the middle of processing trace data. #0000566 |
| • | Bug fixed: AV when Firebird server can't start a trace session due to missing trace plugins. #0000586 |
| • | Bug fixed: Random AV when duplicating a project with a server as target with no registered databases. #0000587 |
October 31, 2012 - v2.6.1.5
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: Newly added/duplicated event rule nodes haven't been inserted at the expected location. #0000475 |
| • | Bug fixed: Parsing issue in SWEEP trace events. #0000482 |
October 9, 2012 - v2.6.0.10
Enhancements:
| • | Added raw output fragment per trace event in parsed trace data. #0000453 |
| • | Added calculated attribute "Cache Hit Ratio [%]" in parsed trace data. #0000454 |
| • | Added "Description" memo field for a trace project. #0000456 |
| • | Added "Description" memo field in Server Wizard. #0000457 |
| • | Added "Description" memo field in Server Database Wizard. #0000458 |
| • | Persist description per trace session with project description as default. #0000459 |
| • | New "Prompt Description" trace project configuration option to temporarily define a different trace session description when starting a trace session. #0000460 |
| • | Enhancement in Event Processing module: Support for server-based event rules, which fire for each project. #0000462 |
| • | Automatic confirmation dialog to create a new trace project upon attaching to a server with no registered trace project. #0000465 |
| • | Explicitly disallow Trace API attachments to Firebird 2.5.1, due to Firebird Tracker CORE-3656. You still can use Database Monitoring with Firebird 2.5.1 though. #0000466 |
| • | Treat non-existing parsed trace data measures as an empty instead of 0 (e.g. execution time). This leads to a sparsely filled trace data grid, which makes it easier to spot non-existing information vs. existing data of value 0. #0000467 |
| • | Dismiss empty values in trace data grid from being evaluated when calculating a grid footer aggregate function. #0000468 |
| • | Changed "Trace" and "Audit" as trace type to "User Trace" and "System Audit" in trace session list. #0000469 |
Bug fixes:
| • | Bug fixed: Millisecond part of trace event timestamp isn't persisted in FBTM database. #0000455 |
| • | Bug fixed: Check boxes in project list grid are clickable where they shouldn't. #0000461 |
| • | Bug fixed: Millisecond part of trace event timestamp isn't displayed in parsed trace data grid. #0000463 |
July 31, 2012 - v2.5.4.9
Enhancements:
| • | Support for new Firebird 2.5.2 "log_sweep" trace configuration parameter (also see Firebird Tracker CORE-3656). #0000394 |
| • | Support for new Firebird 2.5.2 SWEEP_* trace events (also see Firebird Tracker CORE-3656). #0000395 |
Bug fixes:
| • | Bug fixed: -1 is stored for RemoteProcessId, if remote process information is not available. #0000396 |
June 6, 2012 - v2.5.3.8
Enhancements:
| • | Support for new Firebird 2.5.2 "log_errors" trace configuration parameter (also see Firebird Tracker CORE-3539). #0000354 |
| • | Support for new Firebird 2.5.2 ERROR AT, WARNING AT trace events (also see Firebird Tracker CORE-3539). #0000365 |
Bug fixes:
| • | Bug fixed: Trace data parser issue when the term "Statement" is part of the remote process name. #0000370 |
| • | Bug fixed: AV when Firebird server returns "Error creating trace session" in case of not being able to start a trace session. #0000371 |
April 16, 2012 - v2.5.2.11
Enhancements:
| • | Support for Firebird 3 trace configuration format. #0000303 |
| • | Support for specifying the Firebird client library at different levels, e.g. in the program configuration for the FBTM3.fdb attachment, server and database registration to be used when attaching to the trace service, for per-database monitoring etc. #0000304 |
| • | Docking capabilities ala Visual Studio across the product. #0000316 |
Bug fixes:
| • | Bug fixed: Double-quotes in exported CSV isn't escaped properly. #0000309 |
| • | Bug fixed: Random AVs, freezes. #0000317 |
| • | Bug fixed: Regression causing the trace raw memo output flickering/repainting a lot. #0000322 |
March 9, 2012 - v2.5.1.35
Enhancements:
| • | Additional per-database monitoring facility called "Database Statistics". This integrates more gstat like output, e.g. data pages, index pages, record versions etc. #0000268 |
| • | Support for ODS 11.1 (Firebird 2.1) monitoring tables. Monitoring tables integration failed with an ODS 11.1 database, because FBTM expected a Firebird 2.5 database with ODS 11.2. #0000269 |
| • | When registering a new server database, pre-set username/password from the server entry. #0000270 |
| • | Support for database size (KB, MB, GB) in "Database" monitoring tables tab. #0000271 |
| • | Ability to fetch the database default character set when registering a database. #0000272 |
| • | Improved performance when closing areas where data grid states are persisted. #0000275 |
| • | Export To CSV: Support in trace data grid and all data grids in per-database monitoring. #0000276 |
| • | Load database header page from file including processing. #0000277 |
| • | Improved performance when filling monitoring table grids. #0000278 |
| • | Pre-select useful trace configuration when creating a new trace project. #0000279 |
| • | Reworked/added context-menus in Database Monitoring area. #0000283 |
| • | One-Click functionality to locate OAT from the header page output in the transaction monitoring table. #0000284 |
| • | Allow re-arranging grid column positions in the grid configuration dialog. #0000291 |
Bug fixes:
| • | Bug fixed: Minor problem in context-sensitive filtering in monitoring table grids. #0000280 |
| • | Bug fixed: Duplicating a server/database entry while it's in connected state, results in unusable new server/database nodes. #0000281 |
| • | Bug fixed: Appending "- Copy" for server host and database name when duplicating doesn't make sense. #0000282 |
| • | Bug fixed: In Monitoring Statements: TransactionID = 0 and Timestamp = 30.12.1899 for empty entries. #0000290 |
February 15, 2012 - v2.5.0.35
Enhancements:
| • | Per-database monitoring capabilities including header page monitoring and Firebird MON$ tables integration. See Database Monitoring. #0000235 |
| • | Database views for easier access to query logon/logoff trace data information. See What's new in V2.5. #0000229 |
| • | Allow to specify a trace column definition file in the trace project. #0000230 |
| • | More appealing way to manage trace session options for an active trace session by using flyout tool panels. #0000232 |
| • | Flyout toolbar panel states are now persisted. #0000253 |
| • | Attempt to make FB TraceManager more Firebird 2.5.1 friendly, due to http://tracker.firebirdsql.org/browse/CORE-3636. Not entirely sure if this works reliably. #0000255 |
| • | Increase page buffers value of the FBTM database to 1024. Applies only to new installations. Feel free to adjust the page buffers value for your installation as needed. #0000260 |
Bug fixes:
| • | Bug fixed: Refreshing the registered server area (e.g. when editing a server entry) will loose the connected state of servers. #0000234 |
| • | Bug fixed: FBTM database metadata update might fail, when there are others connections active. Now there is a check in-place, that a metadata update is only executed, if there are no other active connections on the database. #0000256 |
| • | Bug fixed: Exception "A component named tsStartedProject<N> ..." when starting a trace session. #0000259 |
December 20, 2011 - v2.0.8.5
Enhancements:
| • | Purge strategy for raw and parsed trace data implemented to allow FB TraceManager running in 24x7 scenarios. More information on the new project-based options Raw Max Lines, Parsed Max Rows and Parsed Purge Rows is available in the Trace Data Visualization section. (#0000202) |
Bug fixes:
| • | Bug fixed: "Access violation at address 00000000. Write of address 00000000." in random situations. (#0000200) |
| • | Bug fixed: FBTMLoggerSvc: Parsed trace event is always one event behind. (#0000201) |
November 29, 2011 - v2.0.7.1
Enhancements:
| • | Support for EXECUTE_BLR trace event. (#0000195) |
Bug fixes:
| • | Bug fixed: Main window state is always maximized, thus ignores the previously used position and size. (#0000194) |
November 21, 2011 - v2.0.6.1
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: Parser: Execution time in EXECUTE_PROCEDURE_FINISHED processed wrongly. (#0000185) |
| • | Bug fixed: Parser: Number of reads/writes etc ... in COMMIT_RETAINING not processed. (#0000186) |
| • | Bug fixed: Parser: Number of reads/writes etc ... in ROLLBACK_RETAINING not processed. (#0000187) |
| • | Bug fixed: "Number of records fetched" is stored as -1 when it should be 0. (#0000188) |
| • | Bug fixed: Another potential AV upon stopping a busy trace session. (#0000189) |
| • | Bug fixed: Trace data storage transacion isn't committed when stopping a trace session via the trace session list. (#0000190) |
November 18, 2011 - v2.0.5.0
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: Problem in parser handling parameters and detailed statistics for EXECUTE_PROCEDURE_FINISH. (#0000182) |
| • | Bug fixed: Problem in parser handling parameters and detailed statistics for EXECUTE_STATEMENT_FINISH. (#0000183) |
| • | Bug fixed: Problem in parser handling number of reads/writes etc. for EXECUTE_PROCEDURE_FINISH. (#0000184) |
November 15, 2011 - v2.0.4.0
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: Memory usage steadily increases even without visualization enabled. E.g. in the logger Windows service or in the application if "Paused" and "Dismiss when Paused" = ON in the visualization, thus memory usage shouldn't increase in this case. This makes the Windows logger service FBTMLoggerSvc capable to run 24x7 without significant memory usage. The fix also affects FB TraceManager, because less memory is used when adding a lot of trace events to the raw and parsed output. (#0000181) |
November 14, 2011 - v2.0.3.5
Enhancements:
| • | New event rule type "OnExecuteApplication" for executing an application has been added in the Event Processing module. (#0000175) |
| • | New event rule type "OnPlaySound" for playing a (system) sound has been added in the Event Processing module. (#0000176) |
Bug fixes:
| • | Bug fixed: Possible crash in the Trial Edition after exceeding the max. number of allowed parsed trace events. (#0000177) |
November 10, 2011 - v2.0.2.8
Enhancements:
| • | Project-based "re-sort" option for re-sorting newly added parsed rows automatically. (#0000155) |
| • | Allow to set footer band column value as column regex filter. (#0000156) |
| • | In query result set (used in Browse, Reporting, Analysis): Show real CLOB/Memo field content instead of WIDEMEMO. (#0000167) |
| • | Improved application responsitivity with busy trace sessions. (#0000169) |
| • | Replaced memory manager which results in overall slightly improved performance. (#0000170) |
| • | Project-based "Dismiss when paused" option to remove received trace events from the queue when visualization is paused. (#0000173) |
Bug fixes:
| • | Bug fixed: Regex filter in parsed grid fails for input values containing regex filter escape characters. (#0000157) |
| • | Bug fixed: Another race condition when post-processing certain event types leads to trace session abort. (#0000158) |
| • | Bug fixed: In Project Wizard: Trace configuration isn't stored when clicking on Finish without visiting the last wizard page. (#0000159) |
| • | Bug fixed: In Analysis Wizard: "Finish" button isn't enabled after entering a SQL statement. (#0000161) |
| • | Bug fixed: Crash when closing the application while running trace sessions are busy. (#0000162) |
| • | Bug fixed: Occasional "List index out of bounds (-1)" error message with busy trace sessions. (#0000163) |
| • | Bug fixed: Post-processing trace events produces garbage while receiving trace data which leads to exception when log to database is enabled and more. (#0000164) |
| • | Bug fixed: "List index out of bounds (-1)" error message when working with a selected project, trace session after refreshing the list. (#0000165) |
| • | Bug fixed: Double-clicking the module (Browse, Reports, ...) menu items instead of a single-click leads to an exception. (#0000166) |
| • | Bug fixed: FBTMLoggerSvc2: Stored session name is not the logger service session name. (#0000168) |
November 7, 2011 - v2.0.1.1
Enhancements:
| • | None |
Bug fixes:
| • | Bug fixed: In case of an application error, the application crashes instead of showing a detailed exception dialog (stack trace). (#0000147) |
| • | Bug fixed: The exception stack trace file (.elf) isn't placed in the user's application data directory. It now goes into "C:\Users\<account>\AppData\Roaming\FB TraceManager 3" or "C:\Users\<account>\AppData\Roaming\FB TraceManager 3 Lite". (#0000148) |
| • | Bug fixed: Memory leak per received trace event. (#0000149) |
| • | Bug fixed: Rare access violations with certain processed trace event types. (#0000150) |
| • | Bug fixed: Minor memory leaks caused by the Reporting, Analysis and Event Processing module. (#0000151) |
| • | Bug fixed: Number of allocated threads doesn't decrease when stopping a trace session. (#0000152) |
| • | Bug fixed: Crash when stopping a busy trace session. (#0000153) |
October 31, 2011 - v2.0.0.9
Enhancements:
| • | Improved multi-threading capabilities. Especially in the area of synchronizing the GUI with received trace data from background worker threads has been re-written. This should consume less CPU and should not starve the main GUI thread. In general, the application should be more responsive when running several trace sessions at the same time now. (#0000105) |
| • | Minimize to tray option to be found in the Settings. (#0000107) |
| • | Ability to duplicate a server entry. (#0000108) |
| • | Support for regular expression filters in trace session and project list. (#0000109, #0000110) |
| • | Per project option to define the GUI refresh interval (milliseconds) in the newly implemented multi-threading model. (#0000112) |
| • | The raw output visualization has been improved a lot. (#0000111) - Line number - New trace event line can be highlighted with a custom background color - SQL Syntax-Highlighting - Trace event type (PREPARE_STATEMENT, CLOSE_CURSOR ...) keyword highlighting - Trace event raw data folding to collapse/expand trace event data - Support for bookmarks to navigate to user-definable locations easily |
| • | Option in Register Server wizard to auto-connect upon program start. (#0000114) |
| • | Support for all parsed grid columns when copying content to clipboard (context-menu) and not only SQL and execution plan. (#0000116) |
| • | Append "- Copy" text in certain fields in various wizards when duplicating an entity (project, report, analysis ...). (#0000118) |
| • | Context menus in report and analysis manager tree view added. (#0000119, #0000120) |
| • | Footer band in parsed data grid with column-based aggregate functions on numeric columns. (#0000123) |
| • | Locate line in raw data output for a given parsed trace event by double-clicking (or context-menu) a row in the parsed trace data grid. (#0000125) |
| • | Temporary queue received trace data/events in case of paused visualization and process upon resume. This makes the "Add invisible row when paused" option obsolete, thus it has been removed. (#0000126) |
| • | "Cancel" button in transaction active confirmation dialog when closing a trace session tab to cancel closing the tab. (#0000127) |
| • | GUI improvement: Replace splitter with flyout tool panels were applicable. (#0000132) |
| • | Added units ([ms], [pages]) in parsed grid column header caption for certain columns (e.g. Execution time ...). (#0000135) |
| • | Setting a filter in parsed trace data grid from column values in the selected row. (#0000139) |
| • | Show image/icon in header of parsed trace data grid in case of a filtered column. (#0000140) |
Bug fixes:
| • | Bug fixed: Fixed a bug where the parsed grid output and persisted trace events are always one event behind the raw output. (#0000106) |
| • | Bug fixed: Fixed a rare race condition when running multiple trace sessions simultaneously. (#0000113) |
| • | Bug fixed: Rare occasion where a newly added parsed grid row got a white text color. (#0000117) |
| • | Bug fixed: Potential problem when detecting the Firebird version upon server connect. (#0000121) |
| • | Bug fixed: Problem with parser for an unauthorized attach database event, as there is no ROLE information in the trace data included. (#0000122) |
| • | Bug fixed: Rare race condition when pausing visualization while trace data is received/processed. (#0000128) |
| • | Bug fixed: AV when deleting an event rule which is currently in edit mode. (#0000131) |
| • | Bug fixed: Parser has problems when post-processing certain event types (e.g. COMPILE_BLR). (#0000134) |
| • | Bug fixed: In case of an application error, the application crashes instead of showing a detailed exception dialog (stack trace) |
July 22, 2011 - v1.6.0.10
Enhancements:
| • | Windows service based logger application (FBTMLoggerSvc3) has been implemented. It's included in the download package for registerd customers only. Initially it is a trial version and needs to be licensed separately. Check out the FBTMLoggerSvc - Windows Service section. (#0000035) |
| • | Administration of Windows service based logger has been added to the project wizard. Check out the FBTMLoggerSvc - Getting Started section. (#0000036) |
| • | Make trace-session based options (log to database, commit interval ...) available per project. (#0000029) |
| • | Project-based default regex filter values. (#0000032) |
| • | In the server-based project list: Button Browse Trace Data to jump/navigate to the Browse module for the selected project. (#0000034) |
| • | Optimize memory usage in trace data parser. Allocates and frees memory more efficiently now. (#0000040) |
Bug fixes:
| • | Bug fixed: FBTM database metadata update sometimes fails. Querying the database version is now properly closed before executing scripts. (#0000033) |
| • | Bug fixed: Memory leak in trace data parser, which results in out of memory exceptions when running FB TraceManager 3 for a while with active trace sessions. As each trace session holds it's own trace data parser instance, things are getting even worse with an increasing number of active trace sessions. (#0000039) |
| • | Bug fixed: Minor memory leaks. (#0000050) |
May 23, 2011 - v1.5.2.2
Enhancements:
| • | Option to automatically start trace sessions upon server connect. (#0000015) |
| • | Multi-select in project grid to enable start/delete of multiple projects. (#0000016) |
| • | Multi-select in trace session list to resume/suspend/stop multiple trace sessions. (#0000017) |
| • | Clear regex filter functionality implemented. A button / context-menu item in the parsed trace data grid area allows to clear a defined regex filter. (#0000018) |
| • | Confirmation dialog to commit active log database transaction in case of closing the trace session tab sheet. (#0000019) |
| • | Allow regex filter on # column in parsed trace data grid. (#0000020) |
| • | Show "Finish" button in project wizard in all wizard pages. (#0000026) |
Bug fixes:
| • | Bug fixed: Rare AV when closing FB TraceManager 3 with active trace sessions. (#0000014) |
March 21, 2011 - v1.5.1.3
Enhancements:
| • | "Disable Event Processing" option in Parsed tab when running a trace session. (#2311) |
| • | Active/Deactivate all event rules in one step for a particular project. (#2312) |
| • | Persist currently selected tab information in various places across the application. (#2313) |
Bug fixes:
| • | Bug fixed: Alert window caption still shows "Firebird Trace Manager" instead of "FB TraceManager". (#2310) |
| • | Bug fixed: Access violation when closing FB TraceManager 3 in case an event processing alert window has been shown before. (#2313) |
November 30, 2010 - v1.5.0.29
Enhancements:
| • | Due to a trademark issue on the "Firebird" term in the product name, we have renamed our product from Firebird Trace Manager to FB TraceManager 3. This change also includes the group name in the Windows start menu, the location of FB TraceManager 3 user files (database, reporting/analysis files etc.) and more. |
| • | Event processing facility to execute actions on user-defined conditions on parsed trace data. Check out the new Event Processing section. (#2239) |
| • | Support for services trace events. This allows to configure, receive, parse and persist services trace events (backup, restore, get server log, etc.). Check out the Register Project wizard for new services related trace options. New event names introduced in parsed trace data: ATTACH_SERVICE, START_SERVICE, DETACH_SERVICE, QUERY_SERVICE with specific detailed data in columns starting with SERVICE_. (#2235) |
| • | Small icons and list style for displaying registered servers. This makes working with a larger number of registered servers easier. (#2234) |
| • | Preserve data grid states (visible columns, column position, column width, sorted by etc.) after program restart. (#2281) |
| • | Allow copy SQL and execution plan text from parsed trace data grid into clipboard. A new "Copy" menu item with sub-menu items is available in the parsed trace data grid context menu. (#2291) |
| • | Enable selecting visible columns in parsed trace data grid including a way to save/load column definition presets. A new "Visible Columns" menu item is available in the parsed trace data grid context menu. (#2292) |
| • | Column-based case-sensitive/insensitive regular expression filter ability in parsed trace data grid. (#2293) |
| • | New option "Add invisible rows when paused" to configure if invisible rows should be added in case of "Paused" state for parsed trace data grid has been added. (#2294) |
| • | Dataset navigator buttons for each data grid in Browse module. (#2299) |
| • | More intelligent logic with user dialogs in case of failed server registration. (#2304) |
| • | Choose a different server when creating, duplicating a project. (#2305) |
Bug fixes:
| • | Bug fixed: Disconnecting from server doesn't stop trace sessions started by FBTM. (#2232) |
| • | Bug fixed: Closing FBTM doesn't stop trace sessions started by FBTM. (#2233) |
| • | Bug fixed: Raw output isn't get stored, if LogToDatabase option in Parsed tab isn't set. Storing the raw output must be independent of this setting. (#2243) |
| • | Bug fixed: Import fails, if trace data is wrapped in memo component. (#2278) |
| • | Bug fixed: Access violation upon receiving trace data when parsed trace data grid isn't sorted by a column. (#2282) |
| • | Bug fixed: Access violation parsing trace data with statements including date literals. (#2287) |
| • | Bug fixed: Allow keyedit in port spinedit in server wizard dialog. (#2290) |
| • | Bug fixed: Failed database transactions are rolled back without re-raising exception. (#2295) |
| • | Bug fixed: Installer waits until FBTraceManager.exe terminates, if the "Run ..." option has been chosen in the postinstall area. (#2296) |
| • | Bug fixed: Typo in "Nubmer of writes" column header caption in parsed trace data grid. (#2301) |
| • | Bug fixed: Malformed string exception when storing trace data with special character (e.g. Ø) in the FB TraceManager 3 database. (#2303) |
October 4, 2010 (Ready for the Firebird 2.5 launch) - v1.0.1.5
Enhancements:
| • | Firebird 2.5 RC3/Final compatibility. The trace data parser failed due to a minor change in the raw trace output. (#2219) |
| • | Firebird 2.5 Embedded 32-bit Final is now included (previously Beta/RC). (#2225) |
| • | Make use of the Windows user-specific application directory for storing FBTM data. E.g. on Windows 7: C:\Users\<account>\AppData\Roaming\Firebird Trace Manager. (#2214) |
| • | Store client character set in parsed data in the FBTM database. (#2220) |
| • | Added an option for keeping the selection in the parsed trace data grid. (#2222) |
| • | Sticky first column in parsed data grid. (#2223) |
| • | If parsed trace data output is paused, rows are now still added, although invisible. Removing the selection of the Paused checkbox makes all invisible rows visible again. (#2224) |
| • | Improved usability by adding context menus to the various grid views. (#2226) |
Bug fixes:
| • | Bug fixed: Newly inserted parsed row data doesn't necessarily fulfill the currently used grid sort order. (#2221) |
February 10, 2010 - v1.0.0.19 (Initial Release)