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: )

617 reads

Blogs

Measuring What Matters: Operationalizing Data Trust for CDOs

By

Trust is the currency of the data economy. Without it, even the most advanced...

A Small LLM Fail

By

Another test with Copilot in SSMS (v22 P3) that didn’t go so well. This...

SQL Server Versions: Out With the Old, In With the Supported

By

If your production SQL Servers are still running 2016 (or older) you’re basically banking...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

Can Flyway work with GitHub Self-Hosted Runners?

By Rod at work

I work on the CI/CD team. We're considering different applications for helping us with...

SSIS packages failing with a status "ended unexpectedly" (SSL/TLS timeout ?)

By Eric M Russell

We have an issue where SSIS packages are failing with a status of "ended...

Visit the forum

Question of the Day

Slip Streaming Installs

What does a slipstream installation mean?

See possible answers