SUSER_SID() doesn't handle Windows group names longer than 63 characters - by Jon Seigel

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<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 772267 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/26/2012 12:48:14 PM
Access Restriction Public

Description

(This only applies to groups, as the actual limit for the sAMAccountName field is 256 characters. Users have a much smaller limit of 20 characters for this field.)

I was originally using CREATE LOGIN with a new AD group (getting the familiar "Windows NT user or group '...' not found. Check the name again."), and traced the problem back to the SUSER_SID() function -- presumably the logic for converting a login name to a SID is centralized, and so affects more than just what I was trying to do.

I tested against many versions (2005-2012) and editions on both x86 and x64 with the same results.

Since it's taken this long for someone to hit this bug (I couldn't find another instance of it being reported), even if it doesn't end up getting fixed, please document the limit in BOL.
Sign in to post a comment.
Posted by Microsoft on 1/3/2013 at 10:13 AM
Issue will be fixed in next major release.
Posted by Microsoft on 12/3/2012 at 2:43 PM
Hi Jon,

Thanks for pointing this out to us. We will have this bug fixed in the next major version of SQL Server.

Il-Sung Lee.