<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Query Tuning on FromDual GmbH</title><link>https://www.fromdual.com/tags/query-tuning/</link><description>Recent content in Query Tuning 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/query-tuning/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><item><title>Avoid temporary disk tables with MySQL</title><link>https://www.fromdual.com/blog/avoid-temporay-disk-tables-with-mysql/</link><pubDate>Fri, 19 Dec 2014 07:38:16 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/avoid-temporay-disk-tables-with-mysql/</guid><description>&lt;p&gt;For processing &lt;code&gt;SELECT&lt;/code&gt; queries MySQL needs some times the help of temporary tables. These temporary tables can be created either in memory or on disk.&lt;/p&gt;</description></item><item><title>MySQL single query performance - the truth!</title><link>https://www.fromdual.com/blog/mysql-single-query-performance-the-truth/</link><pubDate>Fri, 13 Dec 2013 17:33:44 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mysql-single-query-performance-the-truth/</guid><description>&lt;h1 id="mysql-single-query-performance---the-truth"&gt;MySQL single query performance - the truth!&lt;/h1&gt;
&lt;p&gt;As &lt;a href="https://www.fromdual.com/comment/871#comment-871" title="5.5 vs 5.6 single threaded performance"&gt;suggested by morgo&lt;/a&gt; I did a little test for the same query and the same data-set mentioned in &lt;a href="https://www.fromdual.com/impact-of-column-types-on-mysql-join-performance" title="Impact of column types on MySQL JOIN performance"&gt;Impact of column types on MySQL JOIN performance&lt;/a&gt; but looking into an other dimension: the time (aka MySQL versions).&lt;/p&gt;</description></item><item><title>Do not trust other peoples benchmarks!</title><link>https://www.fromdual.com/blog/do-not-trust-other-peoples-benchmarks/</link><pubDate>Tue, 06 Apr 2021 13:26:06 +0200</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/do-not-trust-other-peoples-benchmarks/</guid><description>&lt;p&gt;Because they do NOT reflect your problems.&lt;/p&gt;
&lt;p&gt;One of our customers upgraded last month from MariaDB 10.2 to MariaDB 10.5. In the same change he also converted all his data warehouse (DWH)/BI tables from MyISAM to Aria. An all this, naturally, without testing. And it miserably failed! And then we were under heavy time pressure to make things working again&amp;hellip;&lt;/p&gt;</description></item></channel></rss>