How to Avoid N+1 Queries: Comprehensive Guide and Python Code Examples
This article describes the N+1 problem that we often find when developers use row by row solutions for querying related data in a database.
2023-06-21
4,983 reads
This article describes the N+1 problem that we often find when developers use row by row solutions for querying related data in a database.
2023-06-21
4,983 reads
This article looks at Window functions and how they can be used to solve problems in a different way from standard aggregate functions.
2023-02-24
6,258 reads
In this article, we are going to talk about nullable and non-nullable columns specifically related to Postgres databases. While the reasons to use nullable or non-nullable columns may seem obvious at first, there are pitfalls associated with each decision that either affect development velocity, affect application performance, or cause downtime. Let's start with definitions. Nullable […]
2023-02-03
16,449 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
I wrote about this several years ago but will contribute again a life hack...
Hi I have this query that is slow during the 'not in' part of...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers