Database Design

External Article

Defusing Database Time Bombs: Avoiding the Need to Refactor Databases

  • Article

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.

2015-03-13

9,069 reads

Blogs

SQL Server instance metadata inventory with PowerShell and SMO

By

SQL Server instance metadata inventory with PowerShell and SMO The purpose...

5 SQL Tricks Worth Remembering Before You Close the Laptop

By

Disclosure: this post may contain links to books as an affiliate link. If you...

Claude Context Window

By

Every Claude conversation has a context window. It is the total amount of text...

Read the latest Blogs

Forums

Celebrating 30 years of PostgreSQL, A Thank you message

By Pat Wright

Comments posted to this topic are about the item Celebrating 30 years of PostgreSQL,...

provisioning sql server via VMware Cloud Foundation

By andreas.kreuzberg

Hello, has anyone here ever provisioned and actually used an MS SQL Server with...

No More Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item No More Deadlocks

Visit the forum

Question of the Day

No More Deadlocks

After detecting deadlocks in SQL Server 2025 and lowering the time threshold for detecting future issues, when does the Database Engine return to the 5s default interval?

See possible answers