SQL Drip 6-"Microsoft does not recognize leap year February 29" & Character "N" role

Original: SQL Drip 6-"Microsoft does not recognize leap year February 29" & Character "N" role

Http://www.cnbeta.com/articles/50580.htm This web page news report that many Microsoft software does not recognize leap year February 29, which contains SQL Server 2008, I am in my own SQL Server 2008 wrote a few sentence test, these statements show can get February 29 this day, do not know according to the news said on this day to install the software will not cause errors.

Select DATEADD (dd,1, ' 28/feb/2008 ') output: 2008-02-29 00:00:00.000select DATEADD (dd,1, ' 28/feb/2004 ') output: 2004-02-29 00:00:00.000select DATEADD (dd,1, ' 28/feb/2000 ') output: 2000-02-29 00:00:00.000  Select DATEADD (dd,1, ' 28/feb/1996 ')

Output: 1996-02-29 00:00:00.000

The SQL statement did not appear to be an exception.

Select N ' Shanghai changning Store '

Precede the string with N to store it in Unicode format when it is stored in the database.
N ' string ' means string is a Unicode string

The format of a Unicode string is similar to a normal string, but preceded by an n identifier (n stands for the International language (national Language) in the SQL-92 standard). The N prefix must be uppercase. For example, ' Michél ' is a string constant and N ' Michél ' is a Unicode constant. Unicode constants are interpreted as Unicode data and are not evaluated using code pages. Unicode constants do have collations that are primarily used to control comparisons and case sensitivity. Assigns the default collation of the current database to a Unicode constant unless the collation is specified with the COLLATE clause. Each character in the Unicode data is stored using two bytes, and each character in the character data is stored with one byte. For more information, see Working with Unicode data.

Unicode string constants support enhanced collations.

SQL Drip 6-"Microsoft does not recognize leap year February 29" & Character "N" role