<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sql on Lorbic</title>
    <link>https://lorbic.com/tags/sql/</link>
    <description>Recent content in Sql on Lorbic</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 31 Jul 2026 23:00:00 +0530</lastBuildDate>
    <atom:link href="https://lorbic.com/tags/sql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Couchbase Index Best Practices and Query Performance Tuning</title>
      <link>https://lorbic.com/couchbase-index-best-practices-performance-tuning/</link>
      <pubDate>Fri, 31 Jul 2026 23:00:00 +0530</pubDate>
      <guid>https://lorbic.com/couchbase-index-best-practices-performance-tuning/</guid>
      <description>&lt;p&gt;Most Couchbase performance tickets I have seen end the same way: someone adds more nodes, the dashboard looks a little better for a week, and the same query shows up in the slow log a month later. The node count was never the problem. The index was.&lt;/p&gt;&#xA;&lt;p&gt;This is a working reference, not an essay. I already wrote &lt;a href=&#34;https://lorbic.com/posts/what-couchbase-taught-me-about-system-thinking/&#34;&gt;the reflective version&lt;/a&gt; of what indexing in Couchbase teaches you about systems in general. This post skips the reflection and gets straight to the decisions: which index type to reach for, how to order composite keys, how to tell if a query is actually using what you built, and which four or five mistakes account for most of the slow queries you will ever debug. Couchbase&amp;rsquo;s own &lt;a href=&#34;https://developer.couchbase.com/tutorial-tuning-tips-and-advice/&#34; target=&#34;_blank&#34;&gt;tuning tutorial&lt;/a&gt; is the primary source for the recommendations below. Every example runs against &lt;code&gt;travel-sample&lt;/code&gt;, the sample bucket Couchbase ships with every install, so you can paste these into your own cluster and see the plan yourself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
