[quote][b]Posted by:[/b] funkbrotha10 Int32[/quote].NET defines that, but SQL Server does not. It is only int. Although that raises another interesting point. The reason you might end up on a dedicated error page after specifically requesting it through your browser is probably because each profile is defined as having an System.Int32 as the memberID [i]in the application logic[/i] (ASP.NET codebehinds/DLLs). So (if and when) validation being preformed in there on the memberID after being pulled from the GET line is unsuccessful in parsing it to a .NET Int32, it would be more efficient to fail early then and there without touching the database. [quote][b]Posted by:[/b] defnop552 So what happens when it reaches that number? Do new members get deleted account numbers?[/quote]After someone tried to sign up, they would likely end up on one of the dedicated error pages like the one Iggy linked, or the Database Exception one. Accounts wouldn't be deleted or overwritten since when the field set to increment (IDENTITY) reaches its max value (2^31 - 1 in this case) + 1, the INSERT statement would throw an exception back to client application (which is how you'd end up on an error page). This is more likely if the INSERT takes place within a transaction as well. [url=http://ideone.com/mpS9U7]It's not like C++ where bits rollover[/url], which is going to be a problem in the [url=http://en.wikipedia.org/wiki/Year_2038_problem]year 2038[/url]. Interestingly, [url=http://techcrunch.com/2009/06/12/all-hell-may-break-loose-on-twitter-in-2-hours/]Twitter also faced this problem a few years ago[/url] too.