[EN] Version 24.3 During the development of this version, the main attention was paid to the work of the SQL editor and that's what was done: 1. We rewrote the code hint (Code AutoCompletion), now it works strictly within the boundaries of the current SQL block. The separation of blocks inside the tooltip is performed according to the general rules for the editor, namely, the create commands are terminated with the / symbol, the rest ; 2. The code prompter now remembers the keys used to generate hints, saves the data to an array and extracts the data from memory the next time the key is entered. (currently working for PostgreSQL DBMS, the rest of the DBMS will be added in the next version) Points 1 and 2 actually increase the performance of the code hint many times over! 3. Information about the column data type in the form of a code has been added to the grid in the column headers. 4. The data type is displayed in the grid in the column hint 5. Well, we tweaked the code to optimize the column width when uploading data to the grid. Version 24.2 Fixes for identified bugs in version 24.1 • Expanding the list of supported keys for a language pack • The query editor for the MSSQL DBMS has been improved • Changing the program operation logging system. Data is written to a file on disk and to memory structures without accessing the vlc components. • Added program log rotation by date • Extending the functionality of the Form Wizard to support the ability to create custom forms that integrate into various query editor menus (support for all query editor menus for PostgreSQL and MySQL DBMSs). Version 24.1 • Add: SQL editor update for MySQL DBMS • Add: switching the MySQL editor to a single connection manager • Add: language pack editor in table form. Allows you to quickly create translations. • Update: Default style change • Update: SQL editor engine performance has been improved • Add: Removed the modal password entry window and moved it to the main form • Add: Added the ability to change the font name in the query editor. Version 23.4 Identified bugs have been fixed Query editor • The query editor has been speeded up • ctrl+s - save the current sheet to a file on disk (tmp directory) • ctrl + mouse click - displays the code of an object (table, function, view) [PostgreSQL] • new structures in memory for storing operating parameters to speed up work • when you click the mouse in the editor window, information about the pointer position is displayed in the status bar • fix: fixed a bug with de-highlighting selected text CerebroSQL cluster • * shared database configurator updated • * password manager support Version 23.3 • Fix: Исправлена ошибка в функционале перетаскивания имени объекта из дерева в поле ввода SQL. Ошибка заключается в не корректном определении позиции в случаи если произошла прокрутка листа • Fix: Изменен приоритет уровней для подсказчика кода, для случая если в БД есть схема с аналогичным названием, с БД на схему • Add: Оптимизировано использование памяти подсказчиком кода, а так же повышена производительность его работы • Add: Переписано хранилище паролей. Введено понятие пространства, поддержка работы в режиме с центральной базой • Add: Переписана система хранения "шаблонов кода" для редактора запросов. Переход на концепцию пространств. Поддержка многоуровневого дерева Version 23.2 Add: Added the SQL$PG$AUTO_COMMIT parameter to enable/disable the autocommit mode for connecting a sheet of the query editor for PostgreSQL DBMS Add: Added dragging the object name (with schema) from the object tree to the code entry field Query Editor Fix: Speed up work, increased responsiveness of the SQL input window by disabling some of the background processes that do not affect the work Document storage Complete rethinking of the module. • Added concept of space - top-level grouping of documents. • Each document opens in a new sheet • When the program starts, all open documents of the last session are restored. • Added the ability to put documents in "Favorites" • Updated design Version 23.1 Bug: Fixed error "ERROR: near "err_text": syntax error " when viewing the history of executed queries in central database mode Bug: fixed error when deleting an entry in the "Data transfer (lite)" tree - the entry is deleted, but the information in the tree is not displayed Bug: added sorting by name of VIEW node records in the query editor for PostgreSQL DBMS Bug: Fixed problem with program running in wine environment on Astra Linux OS Add: MSSQL table code output switched to separate popup window Add: unified code execution functions in the query editor (single execution process logging format) Add: Added the cdwid parameter (id of the connection to the CDW database) in the CerebroSQL.ini parameter file. The parameter provides automatic connection to the central storage at the program start Add: the output of the program operation log is highlighted in color Add: Data transfer (lite) - logging format reduced to a single one (highlighting lines with color, output format) Add: Data transfer (lite) - updated module interface Add: Data transfer (lite) - added parameter to $DATE (date format in file name yyyymmddhhmiss) for case of data export to CSV file Add: 2 new object classes have been added to the interface language editor (Error description - error message when executing the program, TreeView node - text of nodes in trees) Add: accelerated program loading Fix: fixed generation of select, insert code for PostgreSQL tables displaying deleted columns Fix: Default language pack renamed to DEFAULT Version 22.4 Add: local database markup scripts have been moved to a separate meta-storage. Add: Central database markup scripts (PostgreSQL) moved to a separate meta-storage. Add: updated dashboard of the main program window [1] Add: new program language editor (completely revised approach, coverage of modules will be gradual) [2] Add: code review - optimization of algorithms Add: accelerated program loading Add: convert program to platform (beta operation mode) • The functionality of the "Wizard for creating forms for MDM" has been expanded - it allows you to create both separate windows for the program (call from various menus of the main window and the query editor), and "applications" - groups of combined windows • Data for custom window elements is retrieved from SQL databases by queries Version 22.3 Add: Added creation of the tnsnames.ora file when clicking the "Edit tnsmanes.ora" button in the connection editor if there is no directory file indicated by the path in the TNS_ADMIN field Add: Switching the query editor for Oracle DBMS to a unified connection manager Add: Updated appearance of the wizard for creating links to external programs Fix: executable file compression up to 32M Fix: Updated components Update from 09/14/2022 Fix: Fixed error when selecting a directory in connection manager Add: Added MDM form setup window Version 22.2 • Add: Refinement of the unified connection manager • Add: Transition to a single connection manager of the data transfer manager (Data transfer: lite) • Add: Transition to a single connection manager of the query editor for PostgreSQL DBMS • Add: deep update of data transfer manager (data transfer: lite) • Add: Code fixes and improvements revealed during the operation of version 22.1 • Bug: fixed error saving output of completed queries in local database Version 22.1 What's new: • AWR: comparison of 2 previously generated reports • SQL developer: Add - view statistics on the use of database functions • SQL developer: Add - rman backup info • RMAN: Add - configure backup options • The window for selecting a connection for the monitoring kernel in the form of a structured tree • Tablespace manager: Add - added current file size column • Viewer ControlFile/PFile: Add - viewing all ControlFile and PFile generated by the program • Settings: Add - added a parameter that controls the choice of the method of connecting to servers using Putty (by IP or by DNS name) • Query history: Updated functional • Bug: fixed a bug with displaying the text of a completed request in the current_history mode in the window for viewing the history of completed requests ---------------------------------------------------------------------------------------------------------- 1. Changed table for storing history 2. Added control buttons: Add SQL to Developer, save to file, Copy clipboard, Add to Project manager Transferring data from the history of completed requests is only possible in manual mode Instructions • Open Query Editor • Create sheet for working with SQLite databases • Press the button "Attach databases" • Set the switch opposite the base "core" • Press the "Attach" button • Execute a request Query editor: search connect - connection search window. It can be opened either by the Search button or by the Ctrl + Y key combination. ---------------------------------------------------------------------------------------------------------- SQL developer for PostgreSQL • Rebuilt object tree • COLUMN node - added a child node with a list of system columns • TABLE node - added DEPEND child node, list of referenced base objects • TABLE node - added CHECK child node, list of constraints-checks • Dragging the table name from the tree into the SQL query input field - a select query is added to the input field to the selected table [RU]

[EN] The Session Manager allows you to monitor the work of processes in the Oracle database. Manage sessions, enable/disable session tracing and more Control buttons • Update the data • Open the Query Editor • Open the Active Session Manager • End a dedicated session (the session is terminated with the immediate key) • Enable dedicated session tracing • Finish tracing the session highlighted in the Eracing is enabled for window (the session should be highlighted in the Eracing is enabled for list) • Enable automatic data updates every 5 seconds. • Turn on the backlight of active sessions and sessions that are in the lock state The Sessions tab SQL query select s.SID,        s.SERIAL#,        s.SCHEMANAME,        s.STATUS,        s.EVENT,        s.SQL_ID,        s.OSUSER,        s.MACHINE,        s.MODULE,        s.SERVER,        s.PORT,        s.LOGON_TIME,        s.TERMINAL,        s.PROGRAM,        s.TYPE,        s.SQL_HASH_VALUE,        s.SQL_EXEC_START,        s.ACTION,        s.BLOCKING_INSTANCE,        s.BLOCKING_SESSION_STATUS,        s.BLOCKING_SESSION,        s.FINAL_BLOCKING_SESSION_STATUS,        s.FINAL_BLOCKING_SESSION,        s.CLIENT_INFO,        s.ROW_WAIT_ROW#,        s.ROW_WAIT_BLOCK#,        s.ROW_WAIT_OBJ#,        s.ROW_WAIT_FILE#,        s.PLSQL_SUBPROGRAM_ID,        s.PLSQL_ENTRY_OBJECT_ID,        s.PLSQL_ENTRY_SUBPROGRAM_ID,        s.PLSQL_DEBUGGER_CONNECTED,        s.PLSQL_OBJECT_ID,        s.RESOURCE_CONSUMER_GROUP   from v$session s The query can be changed in the "Program SQL" editor For all the manager's tabs to work correctly, the following fields must be present in the requests: • SID • SERIAL# • EVENT • SQL_ID The remaining fields can be changed. Viewing the description of the waiting session • Select a session in the session list. • In the "Details" block, double-click on the "Event" item The "Parallel session" tab Displays a list of sessions executing requests in parallel in several threads List of parallel computing sessions SELECT DECODE(px.qcinst_id, NULL, username, ' - '||            LOWER(SUBSTR(pp.SERVER_NAME, LENGTH(pp.SERVER_NAME)-4,4))) "Username",        s.sql_id,        DECODE(px.qcinst_id,NULL, 'QC', '(Slave)') "QC/Slave",        TO_CHAR(px.server_set) "SlaveSet",        s.program,        TO_CHAR(s.SID) "SID",        s.Serial#,        TO_CHAR(px.inst_id) "Slave INST",        DECODE(sw.state,'WAITING', 'WAIT', 'NOT WAIT' ) AS STATE,        CASE sw.state           WHEN 'WAITING' THEN SUBSTR(sw.event,1,30)           ELSE NULL        END AS wait_event,        DECODE(px.qcinst_id, NULL, TO_CHAR(s.SID), px.qcsid) "QC SID",        TO_CHAR(px.qcinst_id) "QC INST",        DECODE(px.server_set,'',s.last_call_et,'') "Elapsed (s)"   FROM gv$px_session px,        gv$session s,        gv$px_process pp,        gv$session_wait sw WHERE px.SID=s.SID(+)    AND px.serial#=s.serial#(+)    AND px.inst_id = s.inst_id(+)    AND px.SID = pp.SID(+)    AND px.serial#=pp.serial#(+)    AND sw.SID = s.SID    AND sw.inst_id = s.inst_id ORDER BY username, DECODE(px.QCINST_ID, NULL, px.INST_ID, px.QCINST_ID),   px.QCSID, DECODE(px.SERVER_GROUP, NULL, 0, px.SERVER_GROUP), px.SERVER_SET, px.INST_ID System statistics on the execution of parallel processes SELECT substr(NAME, 21,length(name)) "name",        VALUE,        ROUND((RATIO_TO_REPORT(VALUE) OVER ())*100, 2) || '%' PERC  FROM V$SYSSTAT WHERE NAME LIKE 'Parallel%' ORDER BY NAME DESC The "Blocking tree" tab Displays sessions in the form of a tree that are waiting for the release of a "resource". The root node in the tree is the session holding the lock SQL query with LOCKS as (select /*+ MATERIALIZE*/ * from gv$lock), S as (select /*+ MATERIALIZE*/ s.* from gv$session s), BLOCKERS as (select distinct L1.inst_id, L1.sid                from LOCKS L1, LOCKS L2               where L1.block > 0                 and L1.ID1 = L2.ID1                 and L1.ID2 = L2.ID2                 and L2.REQUEST > 0),  WAITERS as (select inst_id, sid from S where blocking_session is not null or blocking_instance is not null) select   LPAD(' ', (LEVEL - 1) * 2) || 'INST#' || s.inst_id || ' SID#' || sid as BLOCKING_TREE,   s.sid,   s.serial#,   s.program,   substr(s.USERNAME || ' ' || s.CLIENT_IDENTIFIER,1,40) as USERNAME,   EVENT,   last_call_et,   seconds_in_wait as SECS_IN_WAIT,   blocking_session_status as BLOCK_SESSTAT,   pdml_enabled,   s.sql_id,   s.osuser,   p.spid,   s.machine as CLNT_HOST,   s.process as CLNT_PID,   s.port as CLNT_PORT,   substr(trim(NVL(sa1.sql_text,sa2.sql_text)), 1, 100) SQL_TEXT,   decode(sign(nvl(s.ROW_WAIT_OBJ#, -1)), -1, 'NONE', DBMS_ROWID.ROWID_CREATE(1, s.ROW_WAIT_OBJ#, s.ROW_WAIT_FILE#, s.ROW_WAIT_BLOCK#, s.ROW_WAIT_ROW#)) req_rowid,   p1text || ' ' || decode(p1text, 'name|mode', chr(bitand(p1,-16777216)/16777215)||chr(bitand(p1, 16711680)/65535)||' '||bitand(p1, 65535), p1text) as   p1text,   p1,   p1raw,   p2text || ' ' || decode(p2text, 'object #', o.object_name || ' ' || o.owner || '.' || o.object_name, p2text) as   p2text,   p2 from s  left join gv$sqlarea sa1 on s.sql_id = sa1.sql_id and s.inst_id = sa1.inst_id  left join gv$sqlarea sa2 on s.prev_sql_id = sa2.sql_id and s.inst_id = sa2.inst_id  left join dba_objects o on s.p2 = o.object_id  left join gv$process p on s.paddr = p.addr and s.inst_id = p.inst_id connect by NOCYCLE prior sid = blocking_session and prior s.inst_id = blocking_instance start with (s.inst_id, s.sid)            in (select inst_id, sid from BLOCKERS minus select inst_id, sid from WAITERS) Additional information on sessions When the session is highlighted in grids, the program displays additional data. The program displays information depending on the activity of a particular sheet. Cursors - information about open cursors in the session select oc.sql_text, oc.sql_id from V$OPEN_CURSOR oc, v$SESSION s where oc.saddr=s.saddr and s.sid=$$SID SQL Text - the text of the current SQL query in the session select sql_fulltext from v$sql where sql_id='$$SQL_ID' Session statistics - values of non-zero session system statistics select st.name, se.value from v$sesstat se, v$statname st where se.statistic#=st.statistic# and se.value<>0 and sid=$$SID order by 2 desc Lock - locking objects by the session select distinct blocking_session, event, do.owner||'.'||do.object_name req_object, sql_text from v$session s, dba_objects do, v$sql s where s.ROW_WAIT_OBJ# = do.object_id and s.sql_id = s.sql_id and blocking_session is not null and sid=$$SID Longops - data on the time of execution of long-term operations in the database (reading data from a table, sorting) and the estimated time of completion of the operation SELECT sl.OPNAME, sl.TARGET, s.machine, ROUND(sl.elapsed_seconds/60) || ':' || MOD(sl.elapsed_seconds,60) elapsed, ROUND(sl.time_remaining/60) || ':' || MOD(sl.time_remaining,60) remaining, ROUND(sl.sofar/sl.totalwork*100, 2) progress_pct, sl.MESSAGE FROM v$session s, v$session_longops sl WHERE s.sid = sl.sid AND s.serial# = sl.serial# and s.SID = $$SID order by sl.START_TIME desc Plan - the plan for executing the current request select * from TABLE(DBMS_XPLAN.DISPLAY_CURSOR('$$SQL_ID' )) Rollback - statistics on the usage of the rollback segment for the session SELECT rs.segment_name, round(r.rssize/1024/1024)||' MB' "size", r.status FROM v$transaction t, v$session s, v$rollstat r, dba_rollback_segs rs WHERE s.saddr = t.ses_addr AND t.xidusn = r.usn AND rs.segment_id = t.xidusn AND s.sid = $$SID AND s.serial# = $$SERIAL# ORDER BY t.used_ublk DESC Session wait - statistics on the current session waiting select s.EVENT, s.SECONDS_IN_WAIT, s.P1, s.P1TEXT, s.P2, s.P2TEXT, s.P3 from V$SESSION_WAIT s where sid=$$SID order by SECONDS_IN_WAIT desc SQL Monitoring - данные системного пакета DBMS_SQLTUNE анализирующего процесс выполнение запроса SELECT DBMS_SQLTUNE.report_sql_monitor( sql_id => '$$SQL_ID', type => 'TEXT', report_level => 'ALL') AS report FROM dual Query statistics - statistics on query execution (specific sql_id) select * from V$SQLSTATS where sql_id = '$$SQL_ID' [RU] Менеджер сессий позволяет отслеживать работу процессов в базе данных Oracle. Управлять сессиями, включать/выключать трассировку сессий и многое другое Кнопки управления • Обновить данные • Открыть редактор запросов • Открыть менеджер активных сессий • Завершить выделенную сессию (выполняется завершение сессии с ключом immediate) • Включить трассировку выделенной сессии • Завершить трассировку выделенной в окне Eracing is enabled for сессии (сессия должна быть выделена именно в списке Eracing is enabled for) • Включить автоматическое обновление данных каждые 5 секунд. • Включить подсветку активных сессий и сессий находящихся в состоянии блокировки Вкладка "Sessions" SQL Запрос select s.SID, s.SERIAL#, s.SCHEMANAME, s.STATUS, s.EVENT, s.SQL_ID, s.OSUSER, s.MACHINE, s.MODULE, s.SERVER, s.PORT, s.LOGON_TIME, s.TERMINAL, s.PROGRAM, s.TYPE, s.SQL_HASH_VALUE, s.SQL_EXEC_START, s.ACTION, s.BLOCKING_INSTANCE, s.BLOCKING_SESSION_STATUS, s.BLOCKING_SESSION, s.FINAL_BLOCKING_SESSION_STATUS, s.FINAL_BLOCKING_SESSION, s.CLIENT_INFO, s.ROW_WAIT_ROW#, s.ROW_WAIT_BLOCK#, s.ROW_WAIT_OBJ#, s.ROW_WAIT_FILE#, s.PLSQL_SUBPROGRAM_ID, s.PLSQL_ENTRY_OBJECT_ID, s.PLSQL_ENTRY_SUBPROGRAM_ID, s.PLSQL_DEBUGGER_CONNECTED, s.PLSQL_OBJECT_ID, s.RESOURCE_CONSUMER_GROUP from v$session s Запрос может быть изменен в редакторе "Program SQL" Для корректной работы всех вкладок менеджера необходимо наличие в запросах следующих полей: • SID • SERIAL# • EVENT • SQL_ID Остальные поля могут быть изменены.   Просмотр описания ожидания сессии • Выделить сессию в списке сессий. • В блоке "Details" дважды нажать на пункт "Event" Вкладка "Parallel session" Отображает список сессий выполняющих запросы параллельно в несколько потоков Список сессий выполняющих параллельные вычисления SELECT DECODE(px.qcinst_id, NULL, username, ' - '|| LOWER(SUBSTR(pp.SERVER_NAME, LENGTH(pp.SERVER_NAME)-4,4))) "Username", s.sql_id, DECODE(px.qcinst_id,NULL, 'QC', '(Slave)') "QC/Slave", TO_CHAR(px.server_set) "SlaveSet", s.program, TO_CHAR(s.SID) "SID", s.Serial#, TO_CHAR(px.inst_id) "Slave INST", DECODE(sw.state,'WAITING', 'WAIT', 'NOT WAIT' ) AS STATE, CASE sw.state WHEN 'WAITING' THEN SUBSTR(sw.event,1,30) ELSE NULL END AS wait_event, DECODE(px.qcinst_id, NULL, TO_CHAR(s.SID), px.qcsid) "QC SID", TO_CHAR(px.qcinst_id) "QC INST", DECODE(px.server_set,'',s.last_call_et,'') "Elapsed (s)" FROM gv$px_session px, gv$session s, gv$px_process pp, gv$session_wait sw WHERE px.SID=s.SID(+) AND px.serial#=s.serial#(+) AND px.inst_id = s.inst_id(+) AND px.SID = pp.SID(+) AND px.serial#=pp.serial#(+) AND sw.SID = s.SID AND sw.inst_id = s.inst_id ORDER BY username, DECODE(px.QCINST_ID, NULL, px.INST_ID, px.QCINST_ID), px.QCSID, DECODE(px.SERVER_GROUP, NULL, 0, px.SERVER_GROUP), px.SERVER_SET, px.INST_ID Системная статистика по выполнению параллельных процессов SELECT substr(NAME, 21,length(name)) "name", VALUE, ROUND((RATIO_TO_REPORT(VALUE) OVER ())*100, 2) || '%' PERC FROM V$SYSSTAT WHERE NAME LIKE 'Parallel%' ORDER BY NAME DESC Вкладка "Blocking tree" Отображает в виде дерева сессии ожидающие освобождения "ресурса". Корневой узел в дереве - сессия удерживающая блокировку SQL Запрос with LOCKS as (select /*+ MATERIALIZE*/ * from gv$lock), S as (select /*+ MATERIALIZE*/ s.* from gv$session s), BLOCKERS as (select distinct L1.inst_id, L1.sid from LOCKS L1, LOCKS L2 where L1.block > 0 and L1.ID1 = L2.ID1 and L1.ID2 = L2.ID2 and L2.REQUEST > 0), WAITERS as (select inst_id, sid from S where blocking_session is not null or blocking_instance is not null) select LPAD(' ', (LEVEL - 1) * 2) || 'INST#' || s.inst_id || ' SID#' || sid as BLOCKING_TREE, s.sid, s.serial#, s.program, substr(s.USERNAME || ' ' || s.CLIENT_IDENTIFIER,1,40) as USERNAME, EVENT, last_call_et, seconds_in_wait as SECS_IN_WAIT, blocking_session_status as BLOCK_SESSTAT, pdml_enabled, s.sql_id, s.osuser, p.spid, s.machine as CLNT_HOST, s.process as CLNT_PID, s.port as CLNT_PORT, substr(trim(NVL(sa1.sql_text,sa2.sql_text)), 1, 100) SQL_TEXT, decode(sign(nvl(s.ROW_WAIT_OBJ#, -1)), -1, 'NONE', DBMS_ROWID.ROWID_CREATE(1, s.ROW_WAIT_OBJ#, s.ROW_WAIT_FILE#, s.ROW_WAIT_BLOCK#, s.ROW_WAIT_ROW#)) req_rowid, p1text || ' ' || decode(p1text, 'name|mode', chr(bitand(p1,-16777216)/16777215)||chr(bitand(p1, 16711680)/65535)||' '||bitand(p1, 65535), p1text) as p1text, p1, p1raw, p2text || ' ' || decode(p2text, 'object #', o.object_name || ' ' || o.owner || '.' || o.object_name, p2text) as p2text, p2 from s left join gv$sqlarea sa1 on s.sql_id = sa1.sql_id and s.inst_id = sa1.inst_id left join gv$sqlarea sa2 on s.prev_sql_id = sa2.sql_id and s.inst_id = sa2.inst_id left join dba_objects o on s.p2 = o.object_id left join gv$process p on s.paddr = p.addr and s.inst_id = p.inst_id connect by NOCYCLE prior sid = blocking_session and prior s.inst_id = blocking_instance start with (s.inst_id, s.sid) in (select inst_id, sid from BLOCKERS minus select inst_id, sid from WAITERS) Дополнительная информация по сессиям При выделении сессии в сетках, программа отображает дополнительные данные. Программа отображает информацию в зависимости от активности того или иного листа. Cursors - сведения о открытых курсорах в сессии select oc.sql_text, oc.sql_id from V$OPEN_CURSOR oc, v$SESSION s where oc.saddr=s.saddr and s.sid=$$SID SQL Text - текст текущего SQL запроса в сессии select sql_fulltext from v$sql where sql_id='$$SQL_ID' Session statistics - значения не нулевых системных статистик сессии select st.name, se.value from v$sesstat se, v$statname st where se.statistic#=st.statistic# and se.value<>0 and sid=$$SID order by 2 desc Lock - блокировки объектов сессией select distinct blocking_session, event, do.owner||'.'||do.object_name req_object, sql_text from v$session s, dba_objects do, v$sql s where s.ROW_WAIT_OBJ# = do.object_id and s.sql_id = s.sql_id and blocking_session is not null and sid=$$SID Longops - данные по времени выполнения длительных операций в БД (чтение данных из таблицы, сортировка) и ориентировочное время завершения операции SELECT sl.OPNAME, sl.TARGET, s.machine, ROUND(sl.elapsed_seconds/60) || ':' || MOD(sl.elapsed_seconds,60) elapsed, ROUND(sl.time_remaining/60) || ':' || MOD(sl.time_remaining,60) remaining, ROUND(sl.sofar/sl.totalwork*100, 2) progress_pct, sl.MESSAGE FROM v$session s, v$session_longops sl WHERE s.sid = sl.sid AND s.serial# = sl.serial# and s.SID = $$SID order by sl.START_TIME desc Plan - план выполнения текущего запроса select * from TABLE(DBMS_XPLAN.DISPLAY_CURSOR('$$SQL_ID' )) Rolback - статистика использования сегмента отката для сессии SELECT rs.segment_name, round(r.rssize/1024/1024)||' MB' "size", r.status FROM v$transaction t, v$session s, v$rollstat r, dba_rollback_segs rs WHERE s.saddr = t.ses_addr AND t.xidusn = r.usn AND rs.segment_id = t.xidusn AND s.sid = $$SID AND s.serial# = $$SERIAL# ORDER BY t.used_ublk DESC Session wait - статистика по текущему ожиданию сессии select s.EVENT, s.SECONDS_IN_WAIT, s.P1, s.P1TEXT, s.P2, s.P2TEXT, s.P3 from V$SESSION_WAIT s where sid=$$SID order by SECONDS_IN_WAIT desc SQL Monitoring - данные системного пакета DBMS_SQLTUNE анализирующего процесс выполнение запроса SELECT DBMS_SQLTUNE.report_sql_monitor( sql_id => '$$SQL_ID', type => 'TEXT', report_level => 'ALL') AS report FROM dual Query statistics - статистика по выполнению запроса (конкретного sql_id) select * from V$SQLSTATS where sql_id = '$$SQL_ID'

[EN] During the development of this version, the main attention was paid to the work of the SQL editor and that's what was done: 1. We rewrote the code hint (Code AutoCompletion), now it works strictly within the boundaries of the current SQL block. The separation of blocks inside the tooltip is performed according to the general rules for the editor, namely, the create commands are terminated with the / symbol, the rest ; 2. The code prompter now remembers the keys used to generate hints, saves the data to an array and extracts the data from memory the next time the key is entered. (currently working for PostgreSQL DBMS, the rest of the DBMS will be added in the next version) Points 1 and 2 actually increase the performance of the code hint many times over! 3. Information about the column data type in the form of a code has been added to the grid in the column headers. 4. The data type is displayed in the grid in the column hint 5. Well, we tweaked the code to optimize the column width when uploading data to the grid. [RU] При разработке данной версии основное внимание было уделено работе редактора SQL и вот, что было сделано: 1. Переписали подсказчик кода (Code AutoCompletion), теперь он работает строго внутри границ текущего SQL блока. Разделение блоков внутри подсказчика выполняется по общим правилам для редактора, а именно команды create завершаются символом /, остальные ; 2. Подсказчик кода теперь запоминает используемые ключи для формирования подсказок сохраняет данные в массив и при последующем вводе ключа извлекает данные из памяти. (работает на данный момент для СУБД PostgreSQL, остальные СУБД будут добавлены в следующей версии) Пункты 1 и 2 фактически многократно повышают производительность подсказчика кода! 3. В сетку в заголовки колонок добавлена информация о типе данных колонки в виде кода. 4. В сетке в хинте колонки выводится тип данных 5. Ну и подправили код для оптимизации ширины колонок при загрузке данных в грид.