More generally than just TRANSACTION ISOLATION LEVEL
, SET
statements are session-level so carry through to sub-processes. However, while they can be changed in a subprocess, those changes do not carry back to the calling / parent context.
Please see the MSDN page for SET Statements for plenty more details.
You can test this easily by doing the following:
SSMS Query Tab 1:
-- DROP TABLE ##tmp;
CREATE TABLE ##tmp (Col1 INT);
INSERT INTO ##tmp (Col1) VALUES (1);
BEGIN TRAN
SELECT * FROM ##tmp WITH (HOLDLOCK, TABLOCKX);
WAITFOR DELAY '00:02:00.000'; -- 2 minute timer
ROLLBACK TRAN;
SSMS Query Tab 2:
-- First, highlight the following and run. It will hang. Cancel the query.
-- SELECT * FROM ##tmp;
-- Second, hit F5. It will return the row twice.
-- If the SET command in the EXEC affected the parent process, the 2nd SELECT
-- would hang.
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
EXEC (N' SELECT * FROM ##tmp; SET TRANSACTION ISOLATION LEVEL READ COMMITTED;');
SELECT * FROM ##tmp;