Frequently Asked Questions

SQL quality/performance check is an automatic check to see if SQL statements conform to the standard and have no performance issues.
Approximately 40 quality check target items include factors such as performance degradation, error induction, and standard violations, and only necessary items can be selectively checked.

The inspection method supports real-time inspection at the time of SQL development and batch inspection by the scheduler.
The real-time inspection method is a method in which developers can check SQL quality in real time by providing a plug-in to the development tool, or automatically check the quality of SQL at the time of Commit Push.
The batch inspection method is supported in two forms, and the inspection results can be checked in various forms, and an Excel download function is also provided.
The first inspection method is a method to perform batch inspection by selecting the inspection range of SQL registered in the shape, and
The second inspection method is a method to automatically collect all SQLs executed on the DB server and perform batch inspection.

It is possible. OpenPOP can be linked with the developer's IDE or configuration management system (Git, etc.) to perform real-time quality checks during the SQL writing process or at the time of configuration (source code repository) registration.
It is possible to secure the quality of development SQL by blocking the early registration of SQL with poor quality.

Yes, it is possible.
OpenPOP supports customers by creating inspection rules (rule set) and providing them in data format so that they can use them immediately when applied, if logical inspection is possible according to the customer's SQL coding rules.

It is possible. Dynamic SQL is difficult to analyze in general because the configuration changes at the time of execution depending on the conditions, but OpenPOP has a function that can check the quality of dynamic SQL.

Yes. We provide a function that allows you to easily check the overall status of SQL quality by DB/task/developer at a glance.

OpenPOP provides a function that automatically corrects about 25 quality violations through its own engine for quality violation SQL. This function can be used selectively according to the user's choice, and when automatically correcting quality violations, it provides a function that allows you to easily compare SQL performance before and after correction and check whether data processing is the same.

SQL performance check checks the following items based on the execution plan:
1. SQL execution time 2. Number of blocks used, 3. Number of processing cases, 4. Memory usage, 5. Table Full Scan, 6. Partition Access, etc.
Performance managers can manage SQL performance by selectively setting inspection indicators by DB, task, and SQL for the six inspection items.

It is possible to some extent. OpenPOP uses a static analysis method based on statistical information and SQL structure analysis, so
it can diagnose structural problems in SQL or inefficiencies in execution plans even if there is no actual data in the table.
It also provides a function that can automatically replicate statistical information of an operating DB to a development or verification DB periodically.

Yes, there is. It provides a function that manages the performance change status separately only for SQLs designated by the administrator to prevent failures from occurring.

OpenPOP provides many features that allow you to easily analyze the target and cause of performance degradation by SQL unit or task identifier. It supports searching for overloaded SQL within a module or procedure, analyzing past and present performance trends for performance-degrading SQL, comparing before and after changing execution plans, identifying TOP SQL and new problem SQL, analyzing major SQL threshold exceedances, and taking emergency measures through SQL Profile or SQL Plan Baseline to help you quickly identify and resolve the cause.

Yes. OpenPOP provides numerical performance changes for all SQLs using the table when creating/changing/removing a specific index.

This will allow for early verification of the efficiency and validity of index design and application.
This function can maximize the efficiency of utilizing the function if a separate verification DB is configured to verify the performance of SQL.

Yes. OpenPOP analyzes the execution SQL logs collected from the operating DB over a certain period of time, and selects only the indexes that are not used at all by the actual app and presents them as targets for deletion recommendations.

OpenPOP provides a SQL impact analysis function that basically presents all related SQLs that use this object when a specific table or column is changed, and analyzes whether the performance of the SQL changes. This function can be used for pre-impact simulation before changing a DB object and for performance impact analysis after the change.

This means that SQLs that do not meet the quality criteria can be automatically blocked from being registered in the source code repository (shape management) or reflected in operations.
You can prevent substandard SQLs from being pushed or distributed to the shape management system (Git, etc.) by linking with the CI/CD pipeline.

OpenPOP controls the operational application of SQLs with poor performance through linkage with the configuration management tool.
When requesting the operational application (deployment) of development SQL, the quality and performance of the SQL to be deployed are automatically checked, and if it is determined to be SQL that does not meet the standard, it controls the operational deployment so that it cannot be done.
In addition, when linking to the CI/CD pipeline or Git, SQLs that do not meet the standard are automatically rejected, thereby fundamentally blocking the cause of failures caused by SQLs with poor performance during the operation process, enabling stable DB operation.

In order to manage the distribution control function for performance-degrading SQL, several prerequisite tasks are required.
First, work must be done in conjunction with a tool (storage) that manages the shape of the source SQL.
Second, the basic inspection indicators provided by OpenPOP must be changed to match the customer's performance inspection indicators, if necessary.
Third, an SQL identifier that can identify SQL must be declared in the SQL statement.

OpenPOP supports detection and response to changes in the execution plan of SQL during execution in the following ways:
It detects sudden performance degradation due to changes in SQL execution plans in real time and alerts the person in charge,
and analyzes the difference in execution plans from normal SQL before the plan change and provides a function to quickly resolve performance issues through the automatic registration of SQL Plan Baseline with the previous execution plan.

Yes. OpenPOP provides a function that tracks the change in SQL performance for a certain period of time after the operation reflection (distribution) of a new SQL and immediately alerts the person in charge when a performance degradation phenomenon occurs.
Through the provision of this function, it supports the function to take quick action on new SQL that may cause performance problems.

OpenPOP's 'SQL Performance Change Prediction' feature predicts potential performance degradation of SQLs that are likely to experience performance changes due to changes in statistical information or table structure before starting daily work. This supports preemptive measures for SQLs that are likely to cause failures, thereby preventing DB failures.

Yes. OpenPOP supports early analysis of performance changes by identifying related SQLs when DB parameters or objects are changed through DB environment change (time) analysis and object change (time) analysis functions. 'DB environment change analysis' compares and simulates SQL performance between ASIS DB and TOBE DB when the environment changes, such as database upgrades, to predict changes and support advance improvements. 'Object change analysis' diagnoses the performance impact of object structure changes, such as index addition and partitioning, on related SQLs in advance in the verification DB to minimize operational failures.

OpenPOP can be installed and set up the basic environment within 1~2 days when the installation environment is prepared, and the operating DB stabilization support function can be used immediately after installation.
It takes about 1~2 weeks for SSO, early notification (Alert), and HR system linkage for efficient use of OpenPOP, and
It takes about 1~4 weeks for linkage with a configuration management solution for operational application control of quality/performance non-conformance SQL.

Normally, a separate server is not configured for OpenPOP installation. The customer assigns an available server and installs it. However, since the repository used in OpenPOP uses Oracle DB, the customer must assign a tablespace of a certain size in Oracle DB for OpenPOP.

No.
It is composed of a web-based UI interface, so DBAs, quality managers, performance managers, developers, etc. can easily use it after receiving basic training on each of their utilization functions.

Yes, it supports managing as many DBs as you want.

OpenPOP operates in an agent-less manner without installing agents in the managed DB, so there is almost no direct load or impact on the operating DB.

OpenPOP's basic policy is not to provide site versions.
However, if a feature requested by a client is useful to all customers, it will be upgraded to a universal feature and provided to all customers equally.
If it is a special environment or feature that applies only to the requesting client, we will try to support it through separate consultation.

Basically, the following training is included:
1. User training (customized training for each user role)
2. Administrator technical training (operating environment setup and management)
In special cases, in-depth on-site training is provided separately through consultation.

Currently, only ORACLE DB is supported. We are developing a function to support open source DB as well.

General DB monitoring tools mainly focus on showing real-time resource usage (memory, CPU, I/O) and tracing/analyzing the cause after performance degradation occurs.
On the other hand, OpenPOP provides functions centered on the role of checking the quality and performance of development and operation SQL from the development stage to the entire operation process,
and supporting preemptive measures for SQL expected to cause failures, thereby preventing performance failures in the operation DB. It also provides functions to support rapid decision-making by performing early analysis of the impact of related SQL performance changes when the environment of the operation DB changes.
In addition, it provides various DB/SQL performance optimization support functions such as index automatic design and index and partitioning optimization guides for the operation DB.

Depending on the customer environment and needs, it is supplied in various ways as follows:
1. DB Core License (general purchase method)
2. Subscription (annual subscription type)
3. Term License (period-based usage type)