SQLCLR

SQLServerCentral Article

How to implement SHA-2 in SQL Server 2005 or 2008 with a CLR assembly

  • Article

SQL Server 2012 supports SHA-256 and SHA-512 through the HASHBYTES() function, but earlier versions of SQL Server do not. SHA-256, SHA-384 and SHA-512 can, however, be implemented in SQL Server 2005 or SQL Server 2008 with the CLR assembly described in this article.

(22)

You rated this post out of 5. Change rating

2013-10-07

6,373 reads

External Article

CLR Performance Testing

  • Article

Are Common Language Runtime routines in SQL Server faster or slower than the equivalent T-SQL code? How would you go about testing the relative performance objectively? Solomon Rutzky creates a test framework to try to answer the question and comes up with some surprising results that you can check for yourself.

2011-08-01

2,863 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Concurrency and Baseline Control: Level...

Spending Time in the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spending Time in the Office

Visit the forum

Question of the Day

Multiple Values Inserted

I have this code on SQL Server 2022. What happens when it runs all at once?

DROP TABLE IF EXISTS dbo.Commission
GO
CREATE TABLE dbo.Commission
(id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY
, salesperson VARCHAR(20)
, commission VARCHAR(20)
)
GO
INSERT dbo.Commission
( salesperson, commission)
VALUES
( 'Brian', 12 ),
( 'Brian', 'None' )
GO
 

See possible answers