External Article

Self-maintaining, Contiguous Effective Dates in Temporal Tables

'Temporal' tables contain facts that are valid for a period of time. When they are used for financial information they have to be very well constrained to prevent errors getting in and causing incorrect reporting. This makes them more difficult to maintain. Is it possible to have both the stringent constraints and simple CRUD operations? Well, yes. Dwain Camps patiently explains the whole process.

External Article

Integrating Database Lifecycle Management into Microsoft's Application Delivery Process

In order to automate the delivery of an application together with its database, you probably just need the extra database tools that allow you to continue with your current source control system and release management system by integrating the database into it. If you're using the Microsoft stack, then Redgate's tools can help with some of the difficult database parts of the process, as Jason Crease demonstrates.

Blogs

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

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,...

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