Data is a core part of many businesses both big and small. For example, Facebook stores each user's profile information, including data about their friends and posts within a database system. SQL (short for Structured Query Language) is the programming language that enables developers and database administrators to work with that data.
There are a few frequently used SQL commands you should be familiar with for database work. Not including Data Definition Languages (DDL) or Data Manipulation Language (DML) statements, SQL commands include those to fetch data from tables and views using the SELECT statement. Today's blog will present a couple of the most important queries to know, along with some examples using Navicat Premium as the database client.
In last week's How the MySQL 8 Performance Schema Helps Diagnose Query Deadlocks blog, we had a crash course on Mutexes and Threads, learned about the MySQL Performance Schema, and applied a few queries against it for investigating performance bottlenecks. In today's follow-up will present a different approach to bottlenecks and deadlock investigation using Navicat Monitor.
MySQL 5.5 saw the addition of the performance_schema and information_schema databases. As we saw in last week's blog, tables in information_schema contain statistical information about tables, plugins, partitions, processlist, status and global variables. As the name suggests, the tables of the performance_schema can be utilized to improve performance of our MySQL instances. Just how to do that will be the topic of today's blog. Just like last time, we'll be using Navicat Premium to demo the various queries.
In relational databases, database metadata, such as information about the MySQL server, the name of a database or table, the data type of a column, or access privileges are stored in the data dictionary and/or system catalog. MySQL's provides database metadata in a special schema called INFORMATION_SCHEMA. There is one INFORMATION_SCHEMA within each MySQL instance. It contains several read-only tables that you can query to obtain the information that you are looking for. In today's blog, we'll explore a few practical uses for the INFORMATION_SCHEMA, as demonstrated using Navicat Premium.
If you work regularly with MySQL or MariaDB, then you will probably find Navicat Premium or Navicat for MySQL to be indispensable. In addition to MySQL and MariaDB, Navicat for MySQL also supports a number of cloud services, including Amazon RDS, Amazon Aurora, Oracle Cloud, Google Cloud, Microsoft Azure, Alibaba Cloud, Tencent Cloud and Huawei Cloud. Navicat Premium is a database development tool that allows you to simultaneously connect to MySQL, MariaDB, MongoDB, SQL Server, Oracle, PostgreSQL, and SQLite databases from a single application, and is also compatible with cloud databases. Both help you create views, queries and functions using an easy-to-use GUI interface. Moreover, you can save your work to the Cloud for reuse and collaborating with team members.
In today's blog, I'll be sharing a few tips and tricks for MySQL that you can apply using either Navicat for MySQL or Navicat Premium.
- 2019 (1)
- 2018 (1)
- December (1)
- November (1)
- October (1)
- September (1)
- August (1)
- July (1)
- June (1)
- An Introduction to Database Events (Part 1)
- Manage MySQL Users in Navicat Premium - Part 4: The Privilege Manager tool (2)
- Manage MySQL Users in Navicat Premium - Part 4: The Privilege Manager tool
- Manage MySQL Users in Navicat Premium - Part 3: Configuring User Privileges
- Manage MySQL Users in Navicat Premium - Part 2: Creating a New User
- May (1)
- April (1)
- March (1)
- February (1)
- January (1)
- 2017 (1)
-
About Us
