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 Book of Redgate: SQL Server Central

By

It was neat to stumble on this in the book, a piece by me,...

Git forked

By

Forgive me for the title. Mentally I’m 12. When I started my current day...

Setting FK Constraints in Data Modeler

By

One of the things a customer asked recently about Redgate Data Modeler was how...

Read the latest Blogs

Forums

Microsoft Security Changes and SQL Server

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Microsoft Security Changes and SQL...

Expanding into Print

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Expanding into Print

Downtime Caused by the Postgres Transaction ID Wraparound Problem

By Chandan Shukla

Comments posted to this topic are about the item Downtime Caused by the Postgres...

Visit the forum

Question of the Day

The String Distance I

In SQL Server 2025, what is returned by this code:

SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled.

See possible answers