Difference between revisions of "SQL"
m (→See also) |
(→Backup & restore: restore only a single database from a full dump) |
||
Line 6: | Line 6: | ||
== Backup & restore == | == Backup & restore == | ||
See [[backup]] for details about this as it's doesn't outside the SQL environment so doesn't belong in this article. But don't forget to set the default character set to the same as the dump used when you import the data! | See [[backup]] for details about this as it's doesn't outside the SQL environment so doesn't belong in this article. But don't forget to set the default character set to the same as the dump used when you import the data! | ||
+ | |||
+ | To restore only a single database from a full dump use the following: | ||
+ | <source lang="bash"> | ||
+ | mysql -D DBNAME -o DBNAME < dump.sql | ||
+ | </source> | ||
== Fixing crashed tables == | == Fixing crashed tables == |
Revision as of 14:41, 31 May 2018
SQL (Structured Query Language) is a computer language used to create, retrieve, update and delete data from relational database management systems. SQL has been standardised by both ANSI and ISO.
SQL is commonly spoken either as the names of the letters ess-cue-el, or like the word sequel. The official pronunciation of SQL according to ANSI is ess-cue-el. However, each of the major database products (or projects) containing the letters SQL has its own convention: MySQL is officially and commonly pronounced "My Ess Cue El"; PostgreSQL is expediently pronounced postgres (being the name of the predecessor to PostgreSQL); and Microsoft SQL Server is commonly spoken as Microsoft-sequel-server. See MediaWikiLite for information about SQLite support in MediaWiki, or MSSQL for information about Microsoft SQL Server support. We're now using MariaDB for our SQL server which is a drop-in replacement for MySQL but is fully open source and more efficient too.
Contents
Backup & restore
See backup for details about this as it's doesn't outside the SQL environment so doesn't belong in this article. But don't forget to set the default character set to the same as the dump used when you import the data!
To restore only a single database from a full dump use the following:
mysql -D DBNAME -o DBNAME < dump.sql
Fixing crashed tables
To fix a crashed table just use repair TABLENAME from the MySQL command line, or to automatically scan all tables and fix them run the following from the shell.
mysqlcheck --auto-repair DBNAME -u USER -p
Dealing with duplicates on import
See Backup
Documentation
- SQL Tutorial - A nice tutorial on SQL
- Official MySQL Documentation
- W3C SQL Tutorial (QuickRef)
MySQL vs MSSQL
MySQL News & Information
- Falcon Overview - the new MySQL 6 Falcon storage engine
- MySQL Stored procedures & triggers
RODBC
Using RODBC to interact with R requires the user to configure the system as described in the file README after installing RODBC.
- See
- http://www.unixODBC.org
- http://www.easysoft.com/developer/interfaces/odbc/linux.html (tutorial using unixODBC)
Towards SQL for P2P environments
- PeerPedia
- MediaWikiLite
- The PIER Project
- Prefix Hash Trees
- Skip B-Trees
- Using MySQL as a NoSQL - A story for exceeding 750,000 qps on a commodity server - Yoshinori Matsunobu's blog
Database procedures
- Reset MySQL root password
- Renaming MySQL tables and databases
- Rename a MediaWiki database
- Reset a wiki user password
- Set a user preference
- Manually backup a wiki
- Add a wiki database
See also
- Good thread on table lock problems and solutions
- MariaDB - see PeerPedia Feb 2013 update for more info