Msg 213 Error Sometimes - by mrwoodyman

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 788632 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 5/26/2013 7:54:38 AM
Access Restriction Public

Description

Dear Microsoft I Occasional get the Msg 213 Error Message.

I Under stand what the error means. and How to fix it, but what I do not understand is how my SQL Script can run some times without issues, and then othertimes with this error message.

The last couple of times I have rebooted my Computer and the message does not occur again (without making any alterations to the SQL Script).

I suspect it has something to do with the locking of the file using the Microsoft Skydrive App. 

It Occurs over two Scripts 
Script 1 
CREATE TABLE REGION (
	REGION_ID		INT				NOT NULL UNIQUE IDENTITY,
	REGION_NAME		VARCHAR(2)		NOT NULL,
	REGION_DESC		VARCHAR(20)		NOT NULL,
	PRIMARY KEY		(REGION_ID) );



Scripts 2
INSERT INTO REGION VALUES	('NW', 'North West'),('SW', 'South West'),('MN', 'Mid North'),('MS', 'Mid South'),('NE', 'North East'),('SE', 'South East');

Regards
Andrew Wood
Sign in to post a comment.
Posted by Microsoft on 7/19/2013 at 5:28 PM
Hello,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.
Posted by Martin Smith on 5/27/2013 at 3:57 AM
Not related to your problem but just thought I'd point out that your CREATE TABLE will end up creating two unique indexes on the same column in case that was unintentional. You probably need to supply more details about how to reproduce this issue. e.g. Are you also dropping a version of REGION that has a different definition when you encounter this.
Posted by mrwoodyman on 5/27/2013 at 1:36 AM
Have had the same issues without the use of Skydrive. Usually a reboot (or 10) will allow the scripts to process wihtout error.