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

Local LLM Models at SQL Saturday Boston 2025

By

I’m starting a long trip at Boston this weekend. I’ll be there Saturday speaking,...

3 things you must do to start data quality management right

By

As a data & AI strategist who’s seen countless projects succeed and fail, I...

Set Theory vs. Batch Mode in SQL Server

By

Set Theory vs. Batch Mode in SQL Server Not long ago,...

Read the latest Blogs

Forums

Changing the Recovery Time

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Recovery Time

Getting More Time from AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting More Time from AI

When Page Prefetching Takes a Back Seat – Exploring Trace Flag 652 in SQL Server

By Chandan Shukla

Comments posted to this topic are about the item When Page Prefetching Takes a...

Visit the forum

Question of the Day

Changing the Recovery Time

I want to change the recovery time for a database running on SQL Server 2022. What are my options for setting the value in my ALTER DATABASE statement. If I run this code, what can I use in place of the xxx to define what 12 means? 

ALTER DATABASE Finance 
 SET TARGET_RECOVERY_TIME = 12 xxx;

See possible answers