Editorials

SQLServerCentral Editorial

13 Disasters

This editorial that was originally published on Aug 15, 2007. It is being rerun as Steve is traveling. This editorial looks at the issues that happen in production and how you should perhaps plan for disasters.

You rated this post out of 5. Change rating

2012-06-11 (first published: )

260 reads

SQLServerCentral Editorial

Tuning People?

Database people are used to changing the hardware of the server on which a problem database resides, or making changes to indexes and database settings, but humans and their organisations are far more difficult to tune and optimise than databases.

(6)

You rated this post out of 5. Change rating

2012-06-11

308 reads

Blogs

Microsoft announces new cybersecurity AI multi-model

By

Yesterday, July 27, 2026, Microsoft announced a new cybersecurity effort called Project Perception. Included...

Getting the SQL Server MCP Server Running

By

If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...

Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations

By

Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...

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