Navicat Monitor 3 added support for PostgreSQL, one of the most popular modern relational databases in use today. New features include an SQL Profiler for PostgreSQL instances as well as enhanced Query Analyzer and Long Running Queries pages, both of which were touched upon in the Monitoring PostgreSQL with Navicat Monitor 3.0 blog article. Today's topic will be the Instance Details page.
Navicat Monitor 3 comes packed with a variety of exciting new features. Case in point, you can now create traces that collect query data based on selected filters from the server log. When creating a trace, you can define criteria to filter the data collected by SQL Profiler and set a schedule for executing the trace. In today's blog we'll learn how to create a trace and view its results.
Version 3 of Navicat Monitor has just be released. Unsurprisingly, it packs many outstanding new features, as well as numerous improvements to existing features. One of the most noteworthy changes between version 2 and 3 is added support for PostgreSQL, including an SQL Profiler for PostgreSQL instances.
Today's blog will provide a quick guide on getting setup to monitor your be PostgreSQL instances using Navicat Monitor 3.0.
It seems like only yesterday that Navicat Monitor 2.0 was released, adding great new features to an already stellar product. Now, version 3.0 is introducing yet more outstanding features, including:
- Support monitoring PostgreSQL instances.
- Support SQL Profiler for PostgreSQL instances.
- Enhanced Query Analyzer.
- Enhanced Long Running Queries.
- Many other new features and improvements.
Of course, all of Navicat Monitor's existing functionality remains in place, including:
- Agentless Architecture
- Real-time Performance Monitoring
- See how your instances are currently functioning easily
- Advanced root cause analysis
- Set custom alert thresholds
- Get notifications via email, SMS or SNMP
- Replication Monitoring
- Powerful Query Analyzer
- and more...
In today's blog, we'll be taking a look at the brand new Navicat Monitor 3.0 with the emphasis being on the new features listed above.
Table Names
Naming conventions are a set of rules (written or unwritten) that should be utilized in order to increase the readability of the data model. You may apply these rules when naming anything inside the database, including tables, columns, primary and foreign keys, stored procedures, functions, views, etc. You need not apply rules to all database objects. For instance, it would be perfectly fine to limit naming convention rules to tables and column names. It's really your decision, as using a naming convention is not mandatory, but beneficial nonetheless. This three part series will present some commonly used naming conventions and provide some tips for formulating your own. Part 1 will cover Table names, while Part 2 will focus on column names. Finally, Part 3 will address Naming Conventions for other database objects such as Foreign Keys, Procedures, Functions, and Views.
- 2024 (1)
- 2023 (1)
- 2022 (1)
- 2021 (1)
- 2020 (1)
- 2019 (1)
- 2018 (1)
- 2017 (1)
