INSERT EXEC statement cannot be nested, the Simple Solution
Step-by-step guide to solve the "INSERT EXEC cannot be nested" problem by using a CLR when unit testing stored procedures using the tSQLt framework.
2022-08-19
37,806 reads
Daniel Brink
- Interests: Robotics, Mountain Biking, Kayaking, Raspberry Pi
- Skills: Everything
- Website: https://sqlmedic.com
Blogs
Query multiple Azure SQL Databases
I was sick of changing context in Azure Data Studio while cleaning up things...
KDA: Echoes of Deception - Case 3
By Zikato
The crime spree in Digitown is not ending. This time 20 cars have been...
The Book of Redgate: Do Your Best Work
By Steve Jones
One of our mission statements in the Book of Redgate says: attempt to do...
Forums
Sustainable Procurement Best Practices for ESG-Driven Supply Chains
In today’s business world, Environmental, Social, and Governance (ESG) criteria are no longer optional. Customers, investors,...
Shining a Light on Shadow AI - Responsible Data Protection When AI is Everywhere
Comments posted to this topic are about the item Shining a Light on Shadow...
CAST(VARCHAR(n)) resolved performance issue?
Hi, I would love to hear if anyone can tell me why a CAST...
Question of the Day
The Internals of Writing a Page
In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?
See possible answers