For more convenience, d.side can be configured to reflect the way you use it.
To do that, several parameters can be adjusted using the “Options / Preferences” menu.
The value of these parameters and options is persistently stored on disk in d.side directory.
Preferences #
| Total number of snapshots | Number of snapshots visible in main screen Global Activity chart. Default 40. |
| Refresh interval | Main screen and Analyzers content is refreshed every n seconds, from 2 to 20. Default 5. |
Options #
| Show internal users SQL | SQL statements executed by SYS user can be shown in main screen SQL statements list. |
| Show new SQL between two snapshots | By default, only SQL statements running for at least two snapshots are visible. New fast queries won’t appear, as they don’t consume enough to immediately seem important. |
| Connect to a RAC cluster as standalone instance | Disable d.side RAC layer, gathering data on every node of the cluster. Useful for better performances for example when you use d.side on a RAC cluster without having d.side RAC option subscribed. |
| Keep passwords | Passwords from connection strings can be kept encrypted in the connections history list. Next time you want to connect to the same Oracle instance, you won’t have to enter the password again. |
| Highlight value change | Data in SQL Info or Session Info windows is flashing if its value changed between two snapshots. This way, it’s very easy to check if a session or a query is still of interest or if it does not run anymore. |
| Check new version availability | Check, when starting d.side, if a new d.side release is available. Major option detects new version: from d.side 4 to d.side 5 for example. Minor option also detects new release: from 5.1 to 5.2 for example. |
Appearence #
| User profile | Developer profile only shows SQL queries. DBA profile also shows wait events and Oracle statistics. User profile is chosen when starting d.side for the first time. |
| Chart | Main screen Global Activity chart can be made of Peak or Flat areas. |
Standard Edition #
| Apply SE restrictions to CPU usage | Maximum number of CPU threads allowed in Oracle Standard Edition. Main screen DB CPU usage will be based on this limit, instead of actual CPU count. |
Personal ID #
This tab shows the optional query used to identify a user from Session Info window.
For more details about “Personal Identification” feature, please refer to dedicated document.
Replay #
| Time format | Replay time displayed in Global Activity (to know what snapshot is currently processed) can be: Absolute, like “09:30:00”. This is the default. Relative to the begining of the Replay period, like “+01m30s”. This is often helpful in environments like load-testing or qualification and acceptance, where a same Oracle activity can be run several times with different setups. |
| Periods comparison margin | Margin (in percents) between periods 1 and 2, to consider them equal. For example, if a SQL query takes 3% more time in second period, we can consider that its behaviour did not change between the two periods. From 0 to 20, default 5%. |
| Show gathering job SQL queries | By default, SQL queries executed by Replay capture job are not displayed, in order to focus on your Oracle activity. This flag can allow you to see these queries. |
| Fetch limit | Maximum number of rows to be retrieved from Replay tables into SQL statements lists. Used to save network resources and load time in d.side live main screen, static Replay summary and dynamic Replay screen. From 200 to 25 000, default 1 000. If not activated, no limit applied, all SQL queries are retrieved and displayed. |
Anais #
| Anais report “Top N” queries | Top N number of SQL queries to be processed by Anais report. From 5 to 50, default 10. |
