Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Never use select into in transactions...... Expand / Collapse
Author
Message
Posted Friday, October 12, 2007 10:48 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 11:32 AM
Points: 372, Visits: 414
Comments posted to this topic are about the item Never use select into in transactions......

Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
Post #410134
Posted Monday, February 11, 2008 3:30 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, September 5, 2013 7:04 AM
Points: 1,197, Visits: 294
This is no longer true in SQL Server 2005...

Regards,
Hans Lindgren



Post #453766
Posted Tuesday, February 14, 2012 6:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 11, 2014 2:29 AM
Points: 1, Visits: 157
I have sql2008 r2 with READ_COMMITTED_SNAPSHOT ON.
So, default database isolation level is read commited with row versioning.

If i try this:

--first connection
BEGIN TRAN
SELECT 1 AS test INTO dbo.test

--second connection
SELECT * FROM SYSOBJECTS
OR
SELECT * FROM SYSOBJECTS WITH (NOLOCK) WHERE NAME LIKE '%test%'
This wont work.

So, the sys.objects is not available even if I have snapshot isolation with row versioning.
Is there any solution? I would like to read from sys.objects and test table should not be visible there until commit of first connection.

lp,S
Post #1251855
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse