About the Author
Greg Duffie
Senior Microsoft SQL Server Architect
Greg Duffie is a Senior Microsoft SQL Server Architect with more than 20 years of production database experience across healthcare, legal e-discovery, marketing, and financial services. He has built and maintained tSQLt unit test suites at enterprise scale — including a suite of 1,600+ tests that enabled a major healthcare data platform to move from bi-monthly releases to a two-week sprint cadence. Greg is the founder of 37SOLUTIONS, LLC and writes about SQL Server unit testing from direct, ongoing production experience — not academic examples. At SqlTesting.com, his focus is practical tSQLt implementation: how to structure tests, what edge cases to catch, and how to make unit testing a real part of a SQL Server development workflow.
Experience behind the writing
Enterprise tSQLt at scale
Built and maintained a suite of 1,600+ tSQLt unit tests for a major healthcare data platform — the test coverage that let the team move from bi-monthly releases to a two-week sprint cadence.
20+ years in production
Senior Microsoft SQL Server Architect with more than two decades of production database work across healthcare, legal e-discovery, marketing, and financial services.
Founder, 37SOLUTIONS, LLC
Runs 37SOLUTIONS, the company behind SQLTesting.com, and consults remotely with teams adopting tSQLt and SQL Server CI/CD.
Writes from ongoing practice
Every article here comes from direct, current production experience — how to structure tests, which edge cases to catch, and how to make unit testing a real part of the SQL Server workflow.
Topics covered
- Microsoft SQL Server
- tSQLt
- SQL Server unit testing
- T-SQL
- Database CI/CD
- Test-driven database development
- Jenkins
- Azure DevOps
- GitHub Actions
- Healthcare data platforms
- Legal e-discovery data
- Financial services databases
Corrections & contact
Every article on SQLTesting.com is written by Greg Duffie, not an editorial team, and the code samples are run against real SQL Server instances before publishing. If you find an error, an outdated recommendation, or a sample that no longer works on a current SQL Server or tSQLt version, please say so — corrections are made and noted on the affected article.