Editorials

SQLServerCentral Editorial

Are Triggers a "Legacy" Feature?

It is late evening. Something is wrong with a database. You narrow down the possibilities, getting more frustrated and puzzled. Stay calm. Check the inputs systematically. No! The data going into that table is right, but when you then read it in the table, it's wrong. Why did I stop believing in the supernatural? Then it hits you. Every time it comes as a surprise. They're using triggers. (This editorial was originally published on Nov 10, 2008)

You rated this post out of 5. Change rating

2013-02-19 (first published: )

641 reads

Blogs

10 Things I Hate About Fabric Deployment Pipelines— And Some Alternatives

By

Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...

The Book of Redgate: Evidence

By

We aren’t the only company that does this, but Redgate Software does try to...

When Your Microsoft Fabric Capacity Runs Out: Optimize, Scale Up, Scale Out, or Isolate?

By

Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....

Read the latest Blogs

Forums

The New World Of AI Robots

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New World Of AI...

Logic question in a WHERE clause using IIF?

By DaveBriCam

Thanks in advance, I'm trying to avoid using IIF for performance reasons, but the...

Execute as failure

By pdanes

Security has long been a problem for me. Every time I think I understand...

Visit the forum

Question of the Day

BIT_COUNT() V

What does this return on SQL Server 2025?

select bit_count(null)

See possible answers