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,836 reads
rohin daswani
An Overview of PostgreSQL Window Functions
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,132 reads
Nullable vs Non-Nullable Columns and Adding Not Null Without Downtime in PostgreSQL
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,013 reads
Blogs
A New Chapter: Why I Made the Move from Dayforce to ESO
By gbargsley
A New Chapter: Why I Made the Move from Dayforce to ESO Over the...
Lean Six Sigma – Brief
By Vinay Thakur
When you have a project or system, it has to be optimized, tuned, and...
T-SQL Tuesday #200: Bad Query signals
NO AI was used to generate this content. Grammarly was used to check and...
Forums
Reading Parquet using openrowset
Hi, We are looking out to read parquet file directly from on premise shared...
Impact of Single-Threaded PVS Cleanup on ADR in SQL Server 2019
We want to enable ADR on our SQL Server 2019 instances. I’ve heard that...
Forward Deployed Engineers
Comments posted to this topic are about the item Forward Deployed Engineers
Question of the Day
DBCC CHECKDB Limits II
I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?
See possible answers