External Article

Tuning the Performance of Change Data Capture in SQL Server 2008

Change data capture is a new feature in SQL Server 2008 that provides an easy way to capture changes to data in a set of database tables so these changes can be transferred to a second system like a data warehouse. This document provides guidance on how to configure change data capture parameters to maximize data capture performance while minimizing the performance impact on the production workload. The scope of this document is limited to the capture of change data and the cleanup process. Querying the changed data is out of scope for this white paper.

SQLServerCentral Article

T-SQL Challenge #1

Do you want to improve your T-SQL skills? MVP Jacob Sebastian runs regular challenges to get you to think about how to solve a problem in T-SQL. These run monthly and we have a summary and explanation from challenge #1 to help you learn more about moving data from 3 tables into a specific format.

Blogs

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Designing a Storage Load Test for SQL Server

By

I’ve been doing storage load tests for SQL Server for a long time, both...

Read the latest Blogs

Forums

SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade

By millardus

Hi all Can I get some perspective from the community please on performing in-place...

How Long is a Long I/O?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Long is a Long...

T-SQL Trigonometric Functions in SQL Server

By Imran2629

Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers