Hi,
I found the following Official Documentation where it is explained that the scenario where a query needs to look up all the rows in a table is one of the worst cases, so in my understanding it is a practice to try to avoid and not recommended.
Regarding your concern about how to avoid it at a query level I found this Best Practices documentation where it is explained that one way to avoid this full table scan from happening is by defining a secondary index.
I hope it helps.
On Monday, February 28, 2022 at 9:52:27 AM UTC+1 senth...@gmail.com wrote:
We are using a query which has multiple left outer joins which perform full table scan while running in google cloud spanner database. In which scenarios usually it performs full table scan and how to avoid it in query level?
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3d005d57-c46a-4e95-aea0-35e74c47d865n%40googlegroups.com.
No comments:
Post a Comment