SQL Performance Tips
@SQLPerfTips
Followers
54K
Following
267
Media
166
Statuses
5K
Tips to get best SQL performance. Covering all major SQL databases. https://t.co/pPX9UrXm8p is my book.
Vienna, Austria
Joined April 2011
SQL Performance Explained — A Book For Developers It focuses on what developers need to know. Just 200 pages…yet covering all major databases. https://t.co/fkbYE74LQt
sql-performance-explained.com
SQL Performance Explained: Everything developers need to know about database performance by Markus Winand
8
57
150
Another look into PostgreSQL CTE materialization and non-idempotent subqueries https://t.co/BprzbiV7bU
shayon.dev
A follow-up exploration into PostgreSQL CTE materialization, diving deeper into why non-idempotent subqueries can execute multiple times, leading to unexpected results.
0
3
8
For this WHERE, what index to create? WHERE subsidiary_id = 42 AND last_name LIKE '%INA%' Is (subsidiary_id) enough or should it be (subsidiary_id, last_name)? https://t.co/Ax09WlDtOB
3
1
15
My favorite change is that MariaDB got an improved "WHERE year(...) = ?" rewriting. https://t.co/9liw4kyyp4 In picture: the green check mark used to be yellow, with the "a" footnote: Unconditionally rewritten—even if only a matching function-based index exists
0
1
5
Survey on performance optimization for database systems (2023) https://t.co/hZu8wWoEJy
researchgate.net
PDF | The performance optimization of database systems has been widely studied for years. From the perspective of the operation and maintenance... | Find, read and cite all the research you need on...
0
5
16
#DoYouKnow? If your index is getting too big in size, you can index only a subset of the values using Partial Indexes. Read more here - https://t.co/6aOT5T1Lck
#Databases #SQL
use-the-index-luke.com
Does an index always have to contain all the table rows? You don’t need to index the rows you are never searching for. Messages queues are good example how to use partial indexes in PostgreSQL and...
0
2
9
Improved RCSI Ghost Cleanup in SQL Server 2022 — by Paul White As always, Paul provides deep insight into the SQL Server implementation. https://t.co/Nc0dfTOnXW
sql.kiwi
An example of poor update performance under RCSI as compared with locking read committed. Details of an improvement in SQL Server 2022 that can help avoid the worst effects.
0
0
7
Farm to TABLE: Local(e) Providers https://t.co/0HGYKYWrYC The Doom That Came To PostgreSQL: When Collations Change https://t.co/GmGHx3zwES
0
0
1
If you are not sure what collations are about, please read the entire series by Christophe Pettus: “Gentlemen, this is a 🏈”: Glyphs, Encodings, Collations, and Locales https://t.co/JDJ2Vm0hUs Speaking in Tongues: PostgreSQL and Character Encodings https://t.co/aLHuWPPM68
1
0
3
As sort-based indexes (such as B-Tree) also use collations to establish their row order, the speed of the collation affects the index build time, but not so much the search time as the number of comparisons for a search is very limited.
1
0
0
Collations are a wonderful feature. They solve problems way beyond case-insensitive search: ignoring accents and "numeric" sorting ('10' > '2') are just two more examples. However, they do have a performance impact as shown by this micro-benchmark: https://t.co/UOcEoQA38H
2
7
23
At about this time of the day, I run my open-to-everyone trainings. The last training this year is "SQL Performance Explained", for which I have one spot left. It starts Dec 2nd and is delivered in seven 2-hour long in-person sessions each Mon/Wed/Fri. https://t.co/86X2Fp1igu
0
3
9
For this WHERE, what index to create? WHERE subsidiary_id = 42 AND last_name LIKE '%INA%' Is (subsidiary_id) enough or should it be (subsidiary_id, last_name)? https://t.co/Ax09WlDtOB
3
1
15
SQL Best Practices Every Java Engineer Must Know https://t.co/nVBQxlOT5t [IMHO: not just Java Engineers]
foojay.io
This comprehensive guide dives into the best practices for SQL query optimization, tailored specifically for Java engineers.
0
3
11
TIL about Index-Only Scan for databases ✨ Also I'm in love with this website
use-the-index-luke.com
The index-only scan is one of the most important SQL tuning techniques at all—often bringing factors!
0
1
10
In the meanwhile enjoy a discount for SQL Performance Explained if you don't have it yet: 15YrsAnniversary Only valid when purchasing directly from me (not on Amazon, ...): https://t.co/qE63UZfEEl (but valid for all languages — see language selection at the top).
sql-performance-explained.com
SQL Performance Explained: Everything developers need to know about database performance by Markus Winand
0
5
14
Learn once, benefit forever. These SQL courses take experienced developers a leap forward. Starting on September 10th! https://t.co/EmwREhXHCU
winand.at
The next round of online SQL trainings starts in September. Enroll now!
1
8
21
The WITH clause is useful to write readable SQL. https://t.co/aneUuC5Tmj
modern-sql.com
Complex queries are hard to read. Literate SQL is about writing queries that are as easy to read as a good novel.
1
9
30
There is currently some fuzz about the performance of subqueries vs with clause. Here is my take on it: https://t.co/JvaBXlbxVF
modern-sql.com
Generally the WITH clause performs like views.
0
7
38
This and much more is explained on Use The Index, Luke! https://t.co/Dyc3prEKbU
use-the-index-luke.com
What every developer should know about SQL performance
0
0
6
What every developer should know about SQL performance - Index/Query (mis)match - The first power of indexing: finding data quickly - The second power of indexing: clustering data - The third power of indexing: sorting data
2
9
53