This one has been plaguing me for years: What is the best way to create a dynamic stored procedure that allows null inputs to filter results? Today, while working on another request to come up with a dynamic stored procedure for a specific report a client wants, I had an epiphany. If I use isnull()...

SQL Server has everything you need already in place to accept large, complicated sets of data as parameters in a stored procedure!

There's no such thing as a global variable in SQL Server. So i had to do it differently. Here's how.

What is the elephant in the room of software engineering? We don't know how to tell which of two competing designs is the better. We can't make informed choices between architectures. Software engineering is in need of an enlightenment.

How to programatically retreive the schema returned by a stored procedure and store it in a DataTable.