SQLServerCentral Article

Unlocking Interoperability: A Guide to Foreign Data Wrappers in PostgreSQL and Aurora PostgreSQL AWS RDS

Unlocking Interoperability: A Guide to Foreign Data Wrappers in PostgreSQL and Aurora PostgreSQL AWS RDS As a database professional, I often encounter scenarios where data is fragmented across various systems. In today's distributed IT landscape, it's not uncommon for critical business information to reside in different databases, perhaps an on-premise PostgreSQL instance for legacy applications, […]

SQLServerCentral Editorial

Life's Little Frustrations

As with others, I've had to deal with death in the family recently. Some other family members are dealing with cancer (a few friends too). Happily none of us has recently been a disaster zone, but that's happened too. So yeah, big, nasty scary stuff happens in life. However, for most of us, most of […]

SQLServerCentral Editorial

Databases and Disasters

I was just reading about how the Philippines are working to update their databases in support of faster and better responses in the case of an emergency. While I do volunteer for some of the local emergency services, I'm right at the bottom of the heap as just a radio operator. I don't have any […]

SQLServerCentral Article

When INCLUDE Columns Quietly Inflate Your Transaction Logs

In this article, I wanted to test a common assumption we DBAs make – that adding INCLUDE columns to indexes is harmless. I created a FULL recovery test database with a realistic wide Orders table containing extra large VARCHAR columns to simulate an ERP workload. I ran updates and measured transaction log backup sizes before and after adding INCLUDE columns to a nonclustered index. The results shocked me. The update without INCLUDE columns generated a 10 MB log backup, while the same update with INCLUDE columns produced over 170 MB – a 17x increase in log volume. I explain why this happens: INCLUDE columns are physically stored in index leaf rows, so updates affecting them write bigger log records. I also clarify that updating key columns generates even more log than INCLUDE updates because it involves row movement (delete + insert), but INCLUDE updates still cost more log than if those columns weren’t indexed at all. The takeaway is clear – INCLUDE columns are powerful, but they silently increase transaction log generation, impacting backup sizes, replication lag, and DR readiness. Always measure their real cost before deploying to production.

Blogs

A New Word: Gnossienne

By

gnossienne– n. the awareness that someone you’ve known for years still has a private...

Exploring DiskANN: Part I: Understanding the Algorithm before the disk

By

How I used AI for this postChatGPT to generate images based on info specifically...

Learning Tool – Deepstash

By

A few months ago I started using Deepstash. Deepstash breaks books into the key...

Read the latest Blogs

Forums

Alamat BCA KCP Pondok Bambu Tlp:0821-8200-233

By layanan_Bca88

Telp/WA 62 821-8200-233 Pondok Bambu Center, Jl. Pahlawan Revolusi No.30 Blk A/5-6, RT.2/RW.2, Wil,...

Alamat BCA KCP Klender Telp:0821-8200-203

By m4rt1n4

Telp/WA 62 821-8200-203 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren...

Alamat BCA KCP Pulogadung Trade Centre Tlp:08218200174

By R4nt4u

Telp/WA 62 8218200174 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3,...

Visit the forum

Question of the Day

The Data API Builder MCP Server Tools

The Data API Builder MCP Server, v2.x, includes a number of tools. What actions can these tools perform in your database?

See possible answers