Skip to content
Jeff Humphreys edited this page Aug 4, 2020 · 5 revisions

Plan

Make the most useful free SQLCLR library that can be easily stuffed in any production database.

Make it easy to understand. Well-documented.

Better unit-testing eventually.

Limit it arguments since SQL Server cannot leave optional arguments off function calls.

Identify more interesting aggregates, like possibly taking 2 columns as input and generating a collection of keypairs as a string, or a single string CSV for export. Not trying too hard to limit inputs to 4K for performance, but just NVARCHAR(MAX) everything for easy maintainability.

Functions that some vendors charge for, make these free.

Creative naming rather than trying to align with some staid way that won't challenge anyone. Unique names are easier to remember. So instead of String_Split I have Pieces. Because what is output is a string split into pieces. Plus I don't want to collide with other libraries.

Lots of regex, and specific problems like email and addresses, so I don't have to remember those crazy mini-programs.