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

638 reads

Blogs

Generate Embeddings in SQL with Aurora and Bedrock

By

Most embedding pipelines on AWS have the same shape: a job reads rows out...

Resolving SQL Server Transaction Log Issues Efficiently

By

Transaction log issues are one of the quietest ways a healthy database turns into...

Adding an HTTP MCP Server to VSCode

By

I wrote earlier this week about the SQL MCP Server using the Data API...

Read the latest Blogs

Forums

Symmetric Key Encryption

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Symmetric Key Encryption

The “Successful Login” Dilemma: Why Your Login Auditing Strategy Might Be Hurting Your Server

By Pablo Echeverria

Comments posted to this topic are about the item The “Successful Login” Dilemma: Why...

Building Your Own Software

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Building Your Own Software

Visit the forum

Question of the Day

Symmetric Key Encryption

If I run this statement in SQL Server 2025, how is the password encrypted?

CREATE SYMMETRIC KEY MySymmetricKey
WITH ALGORITHM = AES_256,
KEY_SOURCE = 'My secret key source passphrase',
IDENTITY_VALUE = 'My secret identity value'
ENCRYPTION BY PASSWORD = 'S&perS#cretP@ssword7';
GO

See possible answers