Managing databases tables - Revision history

Vmurrell at 10:08, 14 August 2023

2023-08-14T10:08:06Z

Vmurrell at 11:22, 20 July 2023

2023-07-20T11:22:44Z

Plazarou: /* Cleaning up Old Logs */

2023-02-13T14:33:49Z

‎Cleaning up Old Logs

Plazarou: /* Logging Tables */

2023-02-13T14:33:34Z

‎Logging Tables

Plazarou: /* Logging Tables */

2023-02-13T14:28:37Z

‎Logging Tables

Plazarou: /* Logging Tables */

2023-02-13T14:28:29Z

‎Logging Tables

Plazarou: /* Logging Tables */

2023-02-13T14:27:37Z

‎Logging Tables

Plazarou: /* Logging Tables */

2023-02-13T14:26:55Z

‎Logging Tables

Plazarou: /* Logging Tables */

2023-02-13T14:26:17Z

‎Logging Tables

Plazarou: /* Logging Tables */

2023-02-13T14:25:45Z

‎Logging Tables

@@ Line 1: / Line 1: @@
 [[Category:How_To]]
 [[Category:How_To V11]]
-The Registry persists information, such as settings and structural metadata to a database. The only time you may need to directly modify this database without using the Registry User Interface is to possibly remove unwanted logging information. Generally Metadata Technology does not recommend modifying database tables unless explicitly instructed to do so.
+The Registry persists information, such as settings and structural metadata to a database. The only time you may need to directly modify this database without using the Registry User Interface is to possibly remove unwanted logging information. It is recommended to NOT modify database tables unless explicitly instructed to do so.
 == Logging Tables ==

← Older revision		Revision as of 11:22, 20 July 2023
Line 1:		Line 1:
		+	[[Category:How_To]]
		+	[[Category:How_To V11]]
	The Registry persists information, such as settings and structural metadata to a database. The only time you may need to directly modify this database without using the Registry User Interface is to possibly remove unwanted logging information. Generally Metadata Technology does not recommend modifying database tables unless explicitly instructed to do so.		The Registry persists information, such as settings and structural metadata to a database. The only time you may need to directly modify this database without using the Registry User Interface is to possibly remove unwanted logging information. Generally Metadata Technology does not recommend modifying database tables unless explicitly instructed to do so.

@@ Line 20: / Line 20: @@
 The information in these tables may relate to structural submission or simply a web service query.  It is generally recommended to persist any requests which have a transaction ID against them as these are releated to structural submission, modification or deletion.
-== Cleaning up Old Logs ==
+== Removing Data from the Tables  ==
 It is permissable to delete the contents of the above tables whilst the Registry is running.  If the data from these tables is removed the only effect is that requesting particular data from the activity pages may result in an error message stating that the data is unavailable.

@@ Line 10: / Line 10: @@
 The table '''registry_audit''' stores Audit information for requests received directly to Registry Web Services (e.g. the Data Transformation Web Service) as well as calls directly to the GUI and any Web Services that are called as direct consequence of that (e.g. the front page of the Registry 'overview.html' calls subsequent Web Services ).  The '''registry_logs''' and '''registry_logs_zip''' tables are used for storing logging information which is the information generated by the Registry logger.  This information is usually output to the Apache Tomcat file "FusionRegistry.logs" but can also be stored in the database.
-The information stored in these tables is not particulalary visible to users of the Registry and is generally only accessible when using the "Activity" administration pages where the information can be displayed in a modal like the following:
+The information stored in these tables is not particularly visible to users of the Registry and is generally only accessible by using the "Activity" administration pages, where the information can be displayed in a modal like the following:
 [[File:ModificationModal.png | 250px ]]
@@ Line 20: / Line 20: @@
 The information in these tables may relate to structural submission or simply a web service query.  It is generally recommended to persist any requests which have a transaction ID against them as these are releated to structural submission, modification or deletion.
-So to save space in your database it is recommended to periodically delete any audit and log entries that do not have an associated transaction id.
+== Cleaning up Old Logs ==
 For the Audit table this can be achieved with:

@@ Line 12: / Line 12: @@
 The information stored in these tables is not particulalary visible to users of the Registry and is generally only accessible when using the "Activity" administration pages where the information can be displayed in a modal like the following:
-[[File:ModificationModal.png | 50px ]]
+[[File:ModificationModal.png | 250px ]]
 <p>

← Older revision		Revision as of 14:26, 13 February 2023
Line 15:		Line 15:

	<p>		<p>
		+	<br>

← Older revision		Revision as of 14:26, 13 February 2023
Line 14:		Line 14:
	[[File:ModificationModal.png\|thumb]]		[[File:ModificationModal.png\|thumb]]

		+	<p>

← Older revision		Revision as of 14:25, 13 February 2023
Line 13:		Line 13:

	[[File:ModificationModal.png\|thumb]]		[[File:ModificationModal.png\|thumb]]
		+
		+

	The information in these tables may relate to structural submission or simply a web service query. It is generally recommended to persist any requests which have a transaction ID against them as these are releated to structural submission, modification or deletion.		The information in these tables may relate to structural submission or simply a web service query. It is generally recommended to persist any requests which have a transaction ID against them as these are releated to structural submission, modification or deletion.