What do I do when I get millions of rows in my database?

[iron peak]

As my app grows, certain tables have the potential to get millions of rows. What is the terminology that I need to research to do something where I offload data from one table to another for the sole purpose of preventing the table from getting too large?

Or am I making this too complicated? I have a SQLite table that is going to have millions of rows but they're just basic integers. Is millions of rows OK? I guess querying would get really bad at that point. Ugh. I need a little direction please - thank you! 🙂

I'm keeping track of hundreds of quiz questions and keeping track how many times each user got each question correct. This table is simply relating the user to the question and keeping a count of correct answers.

[iron peak]

ChatGPT says it can handle millions of rows so I think I answered my own question. Just need to figure out how to do indexing and optimize queries.

[rotund topaz]

Millions of rows is few

It all depends on what queries you do and if tables optimized for that

Anyway you should start with analyzing queries, not premature countermeasures