External Article

Six Scary SQL Surprises

The working life of the DBA can be punctuated by surprises, but they aren't generally nice surprises. This is especially true if the DBA is not checking and monitoring the databases for obvious things such as database corruption, and disk space. However, the really scary surprises are less obvious and provide fewer warning signs. Brent Ozar gives six scary surprises that can be avoided by the shrewd DBA.

SQLServerCentral Editorial

Perspective

I find it extremely easy to sometimes lose sight of the important stuff. The day-to-day grind can seriously get in the way. I think this is a big part of how we find ourselves having so many silly intra-organizational turf wars. The developers don’t like how the DBAs do things. The DBAs are frustrated with […]

Blogs

In Memory of Andrew Clarke, AKA Phil Factor

By

One of the parts of getting older that really sucks is I seem to...

Leading Through the Noise: Harnessing Data in the Age of Digital Overload

By

The New Leadership Frontier In today’s digital landscape, leaders are no longer just visionaries....

A New Word: Anderance

By

anderance – n. the awareness that your partner perceives the relationship from a totally...

Read the latest Blogs

Forums

taking the rcsi dive

By stan

Hi, we put together an extract that runs every 15 minutes against what i...

Parameter Sensitive Plan Optimization in SQL Server 2022

By Deepam Ghosh

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization in...

Minimum Change Tracking Retention

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Minimum Change Tracking Retention

Visit the forum

Question of the Day

Minimum Change Tracking Retention

If I am running this code:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON (CHANGE_RETENTION=xxx);
What is the minimum amount of time I can set?

See possible answers