SQL Quality Management | SQLE 3.2312.0 is here!

What is SQLE?

SQLE is a comprehensive SQL quality management platform that covers SQL auditing and management from development to production environments. It supports mainstream open source, commercial, and domestic databases, provides process automation capabilities for development and operation and maintenance, improves online efficiency, and improves data quality.

 

Below are the Release Notes for SQLE 3.2312.0  . 

Main function introduction

Community Edition

1. Support viewing SQL files

Considering that when auditing ZIP files and GIT warehouse files, they may contain multiple files, making it impossible to quickly locate SQL problem points. This issue supports identifying the specific path of SQL when auditing these two SQL sources to facilitate users to quickly locate problems. SQL and modify.

 

2. JetBrains plug-in adapts to SQLE V3 version

Since the interface of  SQLE V3  has changed and the plug-in is still using the old interface, SQLE V3  cannot use the IDE  plug-in normally. This issue has upgraded  the JetBrains plug-in to be compatible with  the V3 version  of SQLE.

3. Suggested optimization of index creation

In this issue, the code of the rules related to index creation has been completely reconstructed to make different suggestions independent of each other, solving the problems of unreasonable and unclear original suggestions and incomplete coverage of scenarios. The specific optimization points are as follows:

• fix defects

  • Fixed the issue where the index sorting suggestions given in Samsung index suggestions were unreasonable;

  • Fixed the problem that when the MySQL version number cannot be parsed, the recommendation is not triggered;

• Increase scene coverage

  • Based on the columns selected by SELECT and covering index conditions, Samsung index suggestions are given;

  • Added suggestions for the use of function indexes or virtual column indexes; improved scenario support for prefix pattern matching;

• Tips for optimization suggestions

  • Prompt the corresponding SQL content in the suggestions to facilitate quick location of problem points.

Enterprise Edition

1. SQL management and control optimization

In this issue, the SQL management and control page has been optimized to improve the ability of SQL management and control. The specific optimization points are as follows:

• Added display of endpoint information and Schema information: Now you can comprehensively view detailed data source information of SQL on the SQL management and control page, so that you can more accurately judge the urgency of problematic SQL;

• Optimize inefficient query SQL: We have solved the problem of existing page lags, improved the efficiency of query SQL, and enabled you to use SQL to control pages more smoothly;

• Supports SQL analysis: When you find problematic SQL on the control page, you can directly refer to the SQL execution plan and audit suggestions to more accurately determine the cause of the problem and shorten the path to problem location.

2. MyBatis audit optimization

In this update, we have improved the audit support for MyBatis file types. The specific optimizations are as follows:

• Support for SQL analysis: You can gain a more complete understanding of the execution of SQL statements with placeholders to better optimize and tune your queries.

• Added a function to check whether SQL containing placeholders uses indexes: You can easily verify whether SQL with placeholders makes full use of appropriate indexes, thereby improving query performance and efficiency.

 

Release information

Community Edition

New features:

• [#2185] JetBrains plug-in adapts to SQLE V3 version

optimization:

• [#2062] Improved audit rules: "Avoid using COUNT(COL)" rule adds support for subquery scenarios

• [#2114] Improved audit rules: Determine whether the SQL parsed from the MyBatis configuration file uses an index

• [#2117] Optimize MySQL index suggestion logic

• [#2155] New rule name fuzzy query for rule template details

Bug fixes:

• [#2127] Fixed the problem of abnormal data source list when creating a work order

• [#2164] Fixed the problem of using a script to start SQLE, the startup failed, but the output was that the startup was successful.

• [#2169] Fix audit rule defects

• [#2138] Fixed the issue where an error is reported when the scan task scans data sources that do not have audit rules enabled.

• [#2125] Fixed the problem that SQL with special characters cannot be audited

Enterprise Edition

optimization:

• [actiontech/sqle-ee/issues/1271] SQL control list adds schema  column display

• [actiontech/sqle-ee/issues/1229] Optimize the display of SQL control endpoint information

• [actiontech/sqle-ee/issues/1294] DB2 Top SQL scan task optimization

• [actiontech/sqle-ee/issues/1266] SQL management page supports SQL analysis

• [actiontech/sqle-ee/issues/1256] SQL analysis function supports SQL parsed from MyBatis files

• [actiontech/sqle-ee/issues/1272] When collecting slow log files, support content filtering by IP

• [actiontech/sqle-ee/issues/1283] Remove redundant log content

Bug fixes:

• [actiontech/sqle-ee/issues/1174] Fix the problem of T DSQL audit rule  panic

• [actiontech/sqle-ee/issues/1230] Fixed the problem of synchronizing slow log audit results to SQL control and causing errors when the same SQL occurs.

• [actiontech/sqle-ee/issues/1291] Fix the problem that the schema of the slow log part of MySQL cannot be extracted in the intelligent scan

• [actiontech/sqle-ee/issues/1282] Fix the issue that the audit button on the SQL workbench page is unavailable

• [actiontech/sqle-ee/issues/1274] Fix the problem of panic when reviewing TDSQL on work orders