> An anomaly is that system data type names are case-sensitive when specified in an IDENTITY
> function.

"Dan Guzman" <guzmanda@nospam-online.sbcglobal.net> wrote in message
news:%23XCc0fX5GHA.3732@TK2MSFTNGP05.phx.gbl...
> An anomaly is that system data type names are case-sensitive when specified in an IDENTITY
> function. The following fails on an instance with a case-sensitive collation. This is one reason
> I always specify data type names in lower case.
>
> SELECT
> IDENTITY(INT, 1, 1) AS Col1,
> 'test' AS Col2
> INTO #t2
> FROM (SELECT 1 AS Col2) t2
> GO
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in message
> news:uzyZlSX5GHA.2208@TK2MSFTNGP04.phx.gbl...
>> Keywords aren't case sensitive. Identifiers (object names) are, with the exception for system
>> datatypes (but sysname is case sensitive, that I've learned the hard way).
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>>
>> "Richard S." <A@B.COM> wrote in message news:OCyrEOX5GHA.696@TK2MSFTNGP06.phx.gbl...
>>> RE:
>>> << Also, this could be a major nightmare if you're dealing with case-sensitive data>>
>>>
>>> Maybe I'm missing something but are *keywords* case sensitive? Per the OP; the desired feature
>>> would affect only keywords, not table or column names etc.
>>>
>>
>
>