External Article

Defusing Database Time Bombs: Avoiding the Need to Refactor Databases

Where applications are evolved by gradually molding them to a growing understanding of the business domain, this presents great challenges to database development. If databases are designed too loosely, and initial errors are allowed to fester, the results become harder and harder to refactor until eventually they constitute a database time bomb. Thomas LeBlanc describes how to avoid a few basic, but very common, database time bombs.

Blogs

ISACA AI Material/Exam Prep Discount (May 18 – June 30, 2026)

By

If you are considering any of the ISACA AI certs like the Advanced Artificial...

A Fabric solution can be very cost effective

By

Are you currently using Microsoft Fabric or considering migrating to it? If so, there...

Track SQL Server Configuration Changes Using the Error Log

By

Track SQL Server Configuration Changes Using the Error Log If you...

Read the latest Blogs

Forums

Before Using AI with Business Data, Read This

By rom_c99

Artificial intelligence tools are quickly becoming part of daily business operations, from document analysis...

Designing SQL Server ETL Pipelines That Don't Break at Scale

By SQL Expert

Comments posted to this topic are about the item Designing SQL Server ETL Pipelines...

Detecting Deadlocks Quickly

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Detecting Deadlocks Quickly

Visit the forum

Question of the Day

Detecting Deadlocks Quickly

In the Database Engine, when a deadlock is detected, what does the detection interval shrink to (in time)?

See possible answers