External Article

The Silent Bug I Find in Most Triggers

I don’t have a problem with triggers. They get the job done when you need to implement business logic in a hurry, and you’re not allowed to change the application. As long as you keep the number of statements to a minimum (say, 2-3), and don’t try to do something really slow like fire up a cursor, triggers can be an efficient way to solve hard problems quickly. However, most triggers I run across have a really, really dangerous bug.

External Article

Overview of Azure Cosmos DB

Cosmos DB is Microsoft’s highly scalable, NoSQL database platform running in Azure. It supports four API models, including Key-Value pair and Documents. Pushpa Sekhara provides an overview of Cosmos DB, including some best practices to improve performance.

Blogs

Scaling PowerShell – Lessons from a Technical Interview

By

Recently, I was in a technical interview where the topic of running PowerShell at...

Installing Old Versions of PowerShell Modules with Their Dependencies

By

I don’t recall where this came up (probably in SQLSlack), but I had a...

In Memory of Andrew Clarke, AKA Phil Factor

By

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

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