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

Data Viz in Fabric Notebooks

By

Lots of people have created Power BI reports, using interactive data visualizations to explore...

App-Consistent MongoDB Snapshots Across Multiple Pure Storage FlashArrays

By

Introduction When you’re running MongoDB at scale with data distributed across multiple Pure Storage...

PASS: Quantum Computing Slides

By

If you're an attendee at the PASS Data Community Summit this year, there are...

Read the latest Blogs

Forums

Filtered Indexes: The Developer’s Secret Weapon in SQL Server

By Chandan Shukla

Comments posted to this topic are about the item Filtered Indexes: The Developer’s Secret...

Is Data Modeling Common?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Is Data Modeling Common?

Getting The Database Name

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting The Database Name

Visit the forum

Question of the Day

Getting The Database Name

I run this code to connect to SQL Server 2022 from the command line.

sqlcmd -S localhost -E
At the command line, I run these two commands:
SELECT ORIGINAL_DB_NAME()
GO
What is returned?

See possible answers