SQLX

01 / The context

The problem behind the project.

Many operational workflows begin and end in SQL Server, yet a file, HTTP call, document, or third-party library can force the workflow into a separate application. SQLX lets database-centered orchestration reach those capabilities while keeping its state, scheduling, permissions, and audit context visible to the SQL developer.

02 / The contribution

How I approached it.

1. Separated orchestration from execution: SQL Server directs the work while an out-of-process runtime executes .NET behavior and returns structured results.
2. Designed CSML, C# Markup Language, as an XML language for expressing executable .NET behavior, with execution able to move to another node.
3. Provided a stored-procedure library as the adoption path: developers can use filesystem, HTTP, document, and API operations without writing the language underneath them.
4. Applied the platform in Client Onboarding, Financial Dashboard, and Tax Dashboard. Kept the public architecture high-level, with deployment and governance fitted to the consuming environment.

03 / The result

What the work made possible.

A product grown from self-funded integration infrastructure begun in 2019. The documented library contains 69 procedures across runtime, .NET, third-party, and API capabilities. It is a SQL-first execution platform—not a UI framework, a universal replacement for services, or a measured productivity multiplier.