Db2 for i & data
Query, edit, compare, import and export the data in Db2 for i.
SQL scripts are checked before you run them.
| Page | What you get |
|---|---|
| SQL & table data | Db2 for i SQL with autocomplete and table data edited in a safe grid. |
| SQL power tools | Generate DDL, run whole scripts, Explain, SQL history and saved queries. |
| Insights | Index advisor, DEV ↔ PROD data compare, message help on hover, job log analyzer. |
| Data, performance & quality | Excel / CSV / JSON import and export, performance monitor, code metrics, RPGUnit tests. |
| Index Advice Chart (3.2) | The indexes Db2 asked for, merged and ranked, with the CREATE INDEX for each. |
| Embedded SQL Statement Statistics (3.3) | How often each SQL statement in your programs ran, how long it took and how often its plan was rebuilt. |
Examples
SQL checks before you run
Risky statements are flagged in every SQL script; Add WHERE 1 = 1 says that every row is really meant.
-- Monthly clean-upDELETE FROM ORDERS;UPDATE CUSTOMER SET REGION = 'EU' WHERE COUNTRY = NULL;DROP TABLE OLD_ORDERS;
Problems
!DELETE without WHERE changes every row of the table. Add a WHERE (or WHERE 1 = 1 if that is really what you want).sql-without-where
!= NULL is never true: use IS NULL.sql-equals-null
iThis statement cannot be undone: check the system and the library first (and keep a copy of the data).sql-irreversible