Bogus language accepted under protested for natively compiled stored procedure - by Erland Sommarskog

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 816418 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 2/2/2014 11:42:57 AM
Access Restriction Public

Description

When you create a natively compiled stored procedure you must specify the language; there is no default. This is somewhat irritating, because most of the time you don't care (and you should not care). However, it turns out that you can specify a bogus language. You get two error messages, but the procedure is nevertheless created. The language appears to be us_english in this case, although I have made investigation from where the default is taken.

Not really sure if this is a bug, but I report it anyway.
Sign in to post a comment.
Posted by Microsoft on 2/20/2014 at 9:09 AM
Thanks for bringing this to our attention.
The procedure creation succeeding in this case is unexpected. We are investigating.

--
Jos de Bruijn - SQL Server PM