Efficient unique Inner Join
If there’s a way to tell Postgres to stop as soon as it knows that each product is available for purchase from at least 1 store on each day.
execution-plan
Why is the optimizer not using the clustering index on my table?
I have this table
Forcing a sequential scan over the index scan
I have this query
Optimizing simple query in PostgreSQL (two table join and sorting)
I have a simple query that should return data about booking, but it misbehaves and sometimes does not return data within 1 minute.
dateadd in the where clause – how can I avoid a full scan in this particular situation?
I have the following query:
Why are the majority of cached plans missing from sys.dm_exec_query_stats?
I’m trying to understand some execution plan caching metadata on a SQL Server 2016 SP3 system, and I can’t reconcile what I’m seeing with the docs.
Execution plan with a lot of ComputeScalar operations
I executed the same query with and without OPTION (RECOMPILE). When I compare the 2 plans, visually the one main difference I see is that the plan without option recompile shows a lot of ComputeScalar operators and the other one doesn’t have any.
Optimizing a PostgreSQL query with many small lookups
I have a database about books and book sales.
The tables look like this:
Optimize filter on SQL query on PostgreSQL
I have a query with a high cost on filtering the results and I am thinking I should be adding an index to optimize the plan, but the indexes I tried till now had no impact. Can I optimize the query by adding composite index for filtered columns?
This is the plan:
Potentially Improper Row Count Read in Parallel Bitmap Hash Match Plan
I am trying to determine whether or not this is an execution plan reporting bug or an actual feature that is working as intended.