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
39,785 reads
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
39,785 reads
Learn how to incorporate Test-Driven Development practices into your database development methodology with TSQLUnit.
2013-11-28 (first published: 2008-10-20)
20,332 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers