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.

SQLServerCentral Article

Cassandra Springboot Integration With Redis

Article Overview In this article we will learn how to integrate a Spring boot application with Apache Cassandra database and Redis cache. This is an extension to one of our previous articles which demonstrates the steps to set up Apache Cassandra and how to integrate is with Springboot, link shared below. https://www.sqlservercentral.com/articles/cassandra-springboot-integration In this tutorial […]

Blogs

SQL Training Black Friday Deals

By

If you're looking for particular "Black Friday" deals, here is what I've seen advertised...

Dry-run xp_delete_file Before Actually Deleting Files?

By

Dry-run xp_delete_file Before Actually Deleting Files? xp_delete_file doesn’t really have a...

Happy Thanksgiving! (USA Holiday)

By

In the United States, today is Thanksgiving. The intent behind the holiday is to...

Read the latest Blogs

Forums

Don't Let Corner Cases Drive Your Design

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Don't Let Corner Cases Drive...

A New Operator

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A New Operator

Troubleshooting Common SQL Server Errors: 823, and 824

By Nisarg Upadhyay

Comments posted to this topic are about the item Troubleshooting Common SQL Server Errors:...

Visit the forum

Question of the Day

A New Operator

In SQL Server 2025, what does this code return? 

SELECT '1' || '0'
 

See possible answers