External Article

Database Design: A Point in Time Architecture

In most relational database implementations. Update and Delete commands destroy the data that was there prior to their issue. However, some systems require that no information is ever physically deleted from or updated in the database. In this article, Arthur Fuller presents a solution to this requirement in the form of a Point-in-Time architecture: a database design which allows a user to recreate an image of the database as it existed at any previous point in time, without destroying the current image.

Blogs

The 2026 Redgate Summit in New York City

By

We’re coming back to New York, which is exciting for me. I love NYC....

Monitoring Fabric Mirroring for SQL 2025

By

I previously wrote about how the underlying technology for Fabric mirroring changed with SQL...

Monday Monitor Tips: Intelligent Alert Thresholds

By

At the recent Redgate Summit in Chicago, I demo’d (lightly) the ML based Alert...

Read the latest Blogs

Forums

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Doing the Little Things

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Doing the Little Things

Visit the forum

Question of the Day

Historical Data Tracking

If I want to track historical data values, which mechanism should I use?

See possible answers