<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Explain on FromDual GmbH</title><link>https://www.fromdual.com/tags/explain/</link><description>Recent content in Explain on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Mon, 16 Jan 2023 08:28:27 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/explain/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating synthetic data sets for tuning SQL queries</title><link>https://www.fromdual.com/blog/creating-synthetic-data-sets-for-tuning-sql-queries/</link><pubDate>Fri, 02 Oct 2020 16:50:33 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/creating-synthetic-data-sets-for-tuning-sql-queries/</guid><description>&lt;p&gt;When it comes to SQL Query tuning with customers we often get the slow running SQL query and possibly, in good cases, also the table structure. But very often, for various reasons, we do not get the data.&lt;/p&gt;</description></item><item><title>Find evil developer habits with log_queries_not_using_indexes</title><link>https://www.fromdual.com/blog/find-evil-developer-habits-with-log-queries-not-using-indexes/</link><pubDate>Wed, 20 Sep 2017 16:00:03 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/find-evil-developer-habits-with-log-queries-not-using-indexes/</guid><description>&lt;p&gt;Recently I switched on the MariaDB slow query logging flag &lt;a href="https://mariadb.com/kb/en/library/server-system-variables/#log_queries_not_using_indexes" target="_blank" title="MariaDB variable log_queries_not_using indexes"&gt;&lt;code&gt;log_queries_not_using_indexes&lt;/code&gt;&lt;/a&gt; just for curiosity on one of our customers systems:&lt;/p&gt;</description></item><item><title>Why you should take care of MySQL data types</title><link>https://www.fromdual.com/blog/why-you-should-take-care-of-mysql-data-types/</link><pubDate>Wed, 25 May 2016 11:42:20 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/why-you-should-take-care-of-mysql-data-types/</guid><description>&lt;p&gt;A customer reported last month that MySQL does a full table scan (FTS) if a query was filtered by a &lt;code&gt;INT&lt;/code&gt; value on a &lt;code&gt;VARCHAR&lt;/code&gt; column. First I told him that this is not true any more because MySQL has fixed this behaviour long time ago. He showed me that I was wrong:&lt;/p&gt;</description></item></channel></rss>