An Implementation of the FNV1a Hash Algorithm for SQL Server
Three CLR-resident functions for 16-, 32-, and 64-bit FNV1a hashing
2012-02-20
5,958 reads
Bret Lowery
TSQL function to detect SQL Agent job state
This article has a T-SQL function to detect the SQL Agent job state.
2012-02-07
9,583 reads
URI Parser: A set of 20 CLR functions for URI parsing
A set of 20 functions for URI and URL parsing, using .NET's native System.Uri parser
2011-07-21
1,476 reads
JSON.SQL: A CLR-resident JSON serializer/deserializer for SQL Server
One CLR function and four CLR procedures for the import/export of JSON data to and from SQL Server are presented, with supporting performance metrics.
2011-07-18
17,696 reads
XLSExport: A CLR procedure to export proc results to Excel
A CLR procedure utilizing the NPOI library to export the results of a passed stored procedure to an Excel spreadsheet.
2011-06-23
10,718 reads
Blogs
Time to Revive our YouTube Channel
It’s been forgotten about and neglected for few years but I’ve decided to dust...
Microsoft MVP 2025: Continuing the Data Platform Journey
I am honored to announce that I have been renewed as a Microsoft MVP...
What is KTLO? Keep The Lights On vs Project Work in Agile
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
Import/Export SSMS Settings issue
I have tried a number of times to export and then import my SSMS...
FQDN - SQL cannot connect when the server name has backslash
Hi I need to connect to a SQL server via FQDN - that is...
Question of the Day
Query Plan Regressions --
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers