Database Tables - Revision history

PeterRobert at 17:55, 20 May 2021

2021-05-20T17:55:34Z

PeterRobert at 17:45, 20 May 2021

2021-05-20T17:45:57Z

PeterRobert at 06:11, 15 May 2021

2021-05-15T06:11:02Z

PeterRobert at 04:58, 25 March 2021

2021-03-25T04:58:43Z

PeterRobert at 06:32, 22 June 2020

2020-06-22T06:32:29Z

PeterRobert at 13:24, 25 October 2019

2019-10-25T13:24:15Z

PeterRobert at 10:16, 23 October 2019

2019-10-23T10:16:56Z

PeterRobert: Created page with "🠈 Back '''[[ADMINISTRATION|🠉 ADMINISTRATION]..."

2019-10-15T06:07:37Z

Created page with "<historylink type="back">🠈 Back</historylink> '''[[ADMINISTRATION|🠉 ADMINISTRATION]..."

New page

<historylink type="back">🠈 Back</historylink>
'''[[ADMINISTRATION|🠉 ADMINISTRATION]]'''
<hr>

<hr>
{{Page_In_Progress}}
{{Contribute}}

@@ Line 9: / Line 9: @@
 *See <big>'''[[phpMyAdmin]]'''</big>
-At the very bottom of the page, you will find a dropdown-menu with some maintenance actions you can preform on any tables selected with the checkboxes.
+At the very bottom of the page, you will find a dropdown-menu with some maintenance actions you can perform on any tables selected with the checkboxes.
-<img database_tables_1_find_maintenance />
+<div class="mainpage_box">
--Hint! Don’t check more than a few, especially if your database is loaded with a lot of data, as the actions might take a while!
 Check Tables works with InnoDB, MyISAM, ARCHIVE and CS. It checks the selected tables for errors, and will output information of errors and warnings. It does not change or fix anything. The desired result is “Status OK”, meaning that there are nothing else to do.
-If you are on InnoDB, you should read the following notes:  https://dev.mysql.com/doc/refman/8.0/en/check-table.html#check-table-innodb
+If you are on InnoDB, you should read the following notes:
-check-table.html#check-table-innodb
-<img database_tables_2_check_tables> Example of a preformed action </img>
+Analyze Tables works with InnoDB, NDB and MyIsam. It analyzes the selected tables and stores the analysis in order to optimize the execution of queries with join-statements. Note, that while the analyze is on-going, the tables are locked for any other operation. The analyze is quick, so it will often not be a problem, but it is important to keep in mind with huge amounts of data. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not performed.
-Analyze Tables works with InnoDB, NDB and MyIsam. It analyzes the selected tables and stores the analysis in order to optimize the execution of queries with join-statements. Note, that while the analyze is on-going, the tables are locked for any other operation. The analyze is quick, so it will often not be a problem, but it is important to keep in mind with huge amounts of data. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not preformed.
+Optimize Tables works with InnoDB, My-ISAM and ARCHIVE, but is less needed for InnoDB than for the other two, due to the way InnoDB stores data. It re-organizes the physical storage of data, which reduces the storage space needed and the speed of gathering data – much like defragmentation on a Windows PC. It is advised to optimize tables after large changes to them; a large change is either a lot of affected rows, or a lot of affected text. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not performed.
-Optimize Tables works with InnoDB, My-ISAM and ARCHIVE, but is less needed for InnoDB than for the other two, due to the way InnoDB stores data. It re-organizes the physical storage of data, which reduces the storage space needed and the speed of gathering data – much like defragmentation on a Windows PC. It is advised to optimize tables after large changes to them; a large change is either a lot of affected rows, or a lot of affected text. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not preformed.
+Example of an action not performed.
-<img database_tables_3_optimize_tables> Example of an action not preformed </img>
+<div class="mainpage_box">
-Repair Tables works with MyISAM, ARCHIVE and CSV. It is the big red emergency-button, and you must make sure to have a backup of your data before pressing it. You should also try out everything else you can think of, before going here, as it may result in a complete loss of data. However, it is very likely to get back all data, especially from a MyISAM table, should it have become corrupted. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not preformed.
+Repair Tables works with MyISAM, ARCHIVE and CSV. It is the big red emergency-button, and you must make sure to have a backup of your data before pressing it. You should also try out everything else you can think of, before going here, as it may result in a complete loss of data. However, it is very likely to get back all data, especially from a MyISAM table, should it have become corrupted. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not performed.
 Convert To UTF-8 does what it says: It converts the encoding of the data into UTF-8, which is recommended, as it supports encoding of special characters.
-Note, that MySQL might change the size of the input-types, in order to prevent data being truncated. As always remember to back-up your data before making changes!
+Note, that MySQL might change the size of the input-types, in order to prevent data being truncated. As always remember to back up your data before making changes!

← Older revision		Revision as of 17:45, 20 May 2021
Line 9:		Line 9:
	*See <big>'''[[phpMyAdmin]]'''</big>		*See <big>'''[[phpMyAdmin]]'''</big>

		+	At the very bottom of the page, you will find a dropdown-menu with some maintenance actions you can preform on any tables selected with the checkboxes.
		+
		+	<img database_tables_1_find_maintenance />
		+
		+	-Hint! Don’t check more than a few, especially if your database is loaded with a lot of data, as the actions might take a while!
		+
		+	Check Tables works with InnoDB, MyISAM, ARCHIVE and CS. It checks the selected tables for errors, and will output information of errors and warnings. It does not change or fix anything. The desired result is “Status OK”, meaning that there are nothing else to do.
		+	If you are on InnoDB, you should read the following notes: https://dev.mysql.com/doc/refman/8.0/en/check-table.html#check-table-innodb
		+	check-table.html#check-table-innodb
		+
		+	<img database_tables_2_check_tables> Example of a preformed action </img>
		+
		+	Analyze Tables works with InnoDB, NDB and MyIsam. It analyzes the selected tables and stores the analysis in order to optimize the execution of queries with join-statements. Note, that while the analyze is on-going, the tables are locked for any other operation. The analyze is quick, so it will often not be a problem, but it is important to keep in mind with huge amounts of data. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not preformed.
		+
		+	Optimize Tables works with InnoDB, My-ISAM and ARCHIVE, but is less needed for InnoDB than for the other two, due to the way InnoDB stores data. It re-organizes the physical storage of data, which reduces the storage space needed and the speed of gathering data – much like defragmentation on a Windows PC. It is advised to optimize tables after large changes to them; a large change is either a lot of affected rows, or a lot of affected text. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not preformed.
		+
		+	<img database_tables_3_optimize_tables> Example of an action not preformed </img>
		+
		+	Repair Tables works with MyISAM, ARCHIVE and CSV. It is the big red emergency-button, and you must make sure to have a backup of your data before pressing it. You should also try out everything else you can think of, before going here, as it may result in a complete loss of data. However, it is very likely to get back all data, especially from a MyISAM table, should it have become corrupted. The desired result is “Status OK”, as any other messages means that something is wrong and the action was not preformed.
		+
		+	Convert To UTF-8 does what it says: It converts the encoding of the data into UTF-8, which is recommended, as it supports encoding of special characters.
		+	Note, that MySQL might change the size of the input-types, in order to prevent data being truncated. As always remember to back-up your data before making changes!

@@ Line 5: / Line 5: @@
 [[File:databasetables.png|link=]]
 </div>
-*This hows a list of the tables in your database.
+*This shows a list of the tables in your database.
 *Do not make any changes here unless you know better!
 *See <big>'''[[phpMyAdmin]]'''</big>

@@ Line 1: / Line 1: @@
-<span class="btn-grey"><historylink type="back">&#129032; Back</historylink></span>
+<div class="btn btn-grey btn-back">{{#fas:arrow-left}} Back</div> <div class="btn btn-grey btn-admin">{{#fas:cog}} Administration</div>
 <hr>
 From admin go to [[File:adminnavbartools.png|link=]] '''Tools &rarr; Database Tables''' to see this:

@@ Line 2: / Line 2: @@
 <span class="btn-grey" style="color:#0088dd;">'''[[ADMINISTRATION|&#x1F809; ADMINISTRATION]]'''</span>
 <hr>
-From admin go to '''Tools &rarr; Database Tables''' to see this:
+From admin go to [[File:adminnavbartools.png|link=]] '''Tools &rarr; Database Tables''' to see this:
 <div class="mainpage_box">
 [[File:databasetables.png|link=]]