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

In Memory of Andrew Clarke, AKA Phil Factor

By

One of the parts of getting older that really sucks is I seem to...

Leading Through the Noise: Harnessing Data in the Age of Digital Overload

By

The New Leadership Frontier In today’s digital landscape, leaders are no longer just visionaries....

A New Word: Anderance

By

anderance – n. the awareness that your partner perceives the relationship from a totally...

Read the latest Blogs

Forums

taking the rcsi dive

By stan

Hi, we put together an extract that runs every 15 minutes against what i...

Parameter Sensitive Plan Optimization in SQL Server 2022

By Deepam Ghosh

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization in...

Minimum Change Tracking Retention

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Minimum Change Tracking Retention

Visit the forum

Question of the Day

Minimum Change Tracking Retention

If I am running this code:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON (CHANGE_RETENTION=xxx);
What is the minimum amount of time I can set?

See possible answers