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

A Pursuit of Lifelong Learning

By

The following came across my YouTube feed today. It’s an interview with General James...

Advice I Like: Time and Focus

By

“You don’t need more time because you already have all the time that you...

Book Review: Microsoft 365 Copilot and Agent Administration Fundamentals

By

I don’t currently manage Microsoft 365 Copilot in an enterprise environment, but it is...

Read the latest Blogs

Forums

What Did Healthy Look Like?

By Laura Copeland

Comments posted to this topic are about the item What Did Healthy Look Like?

DML Trigger Types

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DML Trigger Types

PostgreSQL in action with Opensearch

By sabyda

Comments posted to this topic are about the item PostgreSQL in action with Opensearch

Visit the forum

Question of the Day

DML Trigger Types

How many types of DML triggers are there?

See possible answers