Start Now

Tag: Secondary Indexes

How a Distributed SQL Database Boosts Secondary Index Queries with Index Only Scan

How a Distributed SQL Database Boosts Secondary Index Queries with Index Only Scan

A distributed SQL database reads from remote nodes, which increases the need for optimal data access. From my 20 years of experience as a database consultant, here is the most overlooked optimization technique for any database that supports it: performance-critical queries should find their columns from the index structure, without making extra hops to the table.

Many myths against SQL, such as “joins don’t scale” or “analytic queries need a separate column store”,

Read more

Secondary Index Migration in YugabyteDB

Secondary Index Migration in YugabyteDB

Introduction

YugabyteDB has a great feature in strongly consistent secondary indexes. I have been asked a few times now about how to modify existing indexes. These can range from adding another column to the index or adding another column to the INCLUDE clause. The big question at the end of the day is: how to do this without having to take downtime on the indexes? In this blog post, using the Yugabyte CQL API we will look at how to switch a live running application from using one index to another without a performance hit during the transition,

Read more

YugabyteDB 1.1 New Feature: Speeding Up Queries with Secondary Indexes

YugabyteDB 1.1 New Feature: Speeding Up Queries with Secondary Indexes

Welcome to another post from our ongoing series where we highlight a new feature from the latest 1.1 release! Today we are going to look at secondary indexes.

Defining Secondary Indexes

A database index is a data structure that improves the speed of data retrieval operations on a database table. Typically, databases are very efficient at looking up data by the primary key. A secondary index can be created using one or more columns of a database table,

Read more

A Quick Guide to Secondary Indexes in YugabyteDB

A Quick Guide to Secondary Indexes in YugabyteDB

When creating a Cassandra-compatible YCQL table in the YugabyteDB database, you are required to create a primary key consisting of one or more columns of the table. Primary key based retrievals are efficient because YugabyteDB automatically indexes/organizes the data by the primary key. However, there are many use cases where you may need to retrieve data using columns that are not a part of the primary key. This is where secondary indexes help.

Read more

Learn More to Accelerate Your Retail Business

Ready to dive deeper into distributed SQL, YugabyteDB, and Yugabyte Cloud?
Learn at Yugabyte University
Learn More
Browse Yugabyte Docs
Read More
Join the Yugabyte Community
Join Now