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

Finding Balance: Things Will Come Up

By

I have a presentation on finding balance in your career that got quite a...

Who Are You Doing It For?

By

But as I've matured over the years, I came to realize that I needed...

Presenting Twice in May 2026

By

I will be presenting my latest session, Documenting Your Work for Worry-Free Vacations, in-person...

Read the latest Blogs

Forums

How to change the FDLaunch Error log file location

By schleep

The file FDLAUNCHERRORLOG gets created in the default <instance>\MSSQL\Log folder. So far, I've found...

what data type i should use for roversion col and can i use less than greater

By rajemessage 14195

can i use Rowversioncol ( in my database it's synonyme timestamp is used) to...

Radius Latitude Longitude

By HeftSteady

I have a table with latitude longitude in the format.  45.123456 , -111.123456 ,...

Visit the forum

Question of the Day

A Fun Computer Quote

Which movie featured this quote?

"All programs have a desire to be useful."
Happy April Fools!

See possible answers