Wiki source code of Reset H2 Database
Version 8.1 by Eva Torken on 2024/03/26 13:00
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| |
6.1 | 4 | eMagiz runtimes may contain H2 databases. These databases can need a reset from time to time. This microlearning will guide you throught the process of resetting such H2 databases and will also inform you on the considerations that are important before resetting. |
| |
1.1 | 5 | |
| 6 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 7 | |||
| 8 | == 1. Prerequisites == | ||
| 9 | |||
| 10 | * Intermediate knowledge of the eMagiz platform | ||
| 11 | |||
| 12 | == 2. Key concepts == | ||
| |
7.1 | 13 | This microlearning centers on the reset of a H2 database. |
| |
2.1 | 14 | * The key aspects are: |
| 15 | ** When to use the H2 reset | ||
| |
6.1 | 16 | ** How to perform a H2 reset |
| |
2.1 | 17 | ** Implications of resetting the H2 database. |
| |
1.1 | 18 | |
| 19 | == 3. H2 Database reset == | ||
| |
7.1 | 20 | A reset of the H2 database is used when the database is not performing as expected. This can be because it is retaining the information is it supposed to deliver. It can also be that the database has been unstable and is therefore not performing correctly. |
| |
1.1 | 21 | |
| |
3.1 | 22 | === 3.1 Cloud === |
| |
6.1 | 23 | In short, the reset of a H2 database is described below. |
| |
7.1 | 24 | * The reset of the H2 database does the following: |
| |
3.1 | 25 | ** Removes the H2 databases that are registered under the standard eMgaiz data folder |
| 26 | ** Re-adds the removed H2 databases | ||
| 27 | * With a reset, you start with a clean slate | ||
| 28 | ** H2 databases are emptied | ||
| |
4.1 | 29 | |
| |
3.1 | 30 | [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] |
| |
1.1 | 31 | |
| |
6.1 | 32 | To execute this action please navigate to Deploy -> Architecture. After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called "Reset H2". By pressing this button your executes all steps mentioned above. It is possible to press the 'Reset H2' button for all cloud runtimes, it will however only have an effect if a H2 database exists for the runtime. |
| |
3.1 | 33 | |
| 34 | === 3.2 On-premise === | ||
| |
7.1 | 35 | When the H2 database of an on-premise runtime needs to be reset the action needed is different. Here, the only action needed is to reset the runtime. |
| |
3.1 | 36 | |
| |
4.1 | 37 | For more information on resetting a runtime, please check out the following microlearning: |
| |
5.1 | 38 | * [[Reset runtime>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-reset-runtime.WebHome||target="blank"]] |
| |
6.1 | 39 | |
| 40 | === 3.3 Implications === | ||
| |
7.1 | 41 | Resetting a database has implications. It will remove and re-add all H2 databases on the runtime you have selected. Therefore, all data(messages) on the databases will be lost. This should be taken into account before deciding to reset the H2 databases. |
| |
6.1 | 42 | |
| |
1.1 | 43 | == 4. Key takeaways == |
| 44 | |||
| |
7.1 | 45 | * The 'Reset H2' button empties all eMagiz data folder registered H2 databases |
| 46 | * The 'Reset H2' button is only used for clour runtime, for on-premise runtimes a reset of the runtime is needed | ||
| 47 | * Using the reset button will empty all runtime related H2 databases. Therefore, the messages on the databases will be lost | ||
| |
1.1 | 48 | |
| 49 | == 5. Suggested Additional Readings == | ||
| 50 | |||
| |
8.1 | 51 | * [[H2 Database>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-function-of-h2-database||target="blank"]].))) |
| |
1.1 | 52 | ((( |
| 53 | {{toc/}} | ||
| 54 | ))) | ||
| 55 | {{/container}} | ||
| 56 | {{/container}} |