SQL Server Date Format

In sqlserver2000, convert is used to obtain the processing result of the datetime data type style (full) date data format. Two examples are as follows: CONVERT (varchar (16), time 1, 20: 2007-02-0108:02 * The time is generally the * CONVERT (varchar (10), time 1, 23) Result of the getdate () function or the field * CONVERT (varchar (10) in the data table: 2007-02

In SQL server2000, convert is used to obtain the processing of datetime data format (full). Two examples are as follows: CONVERT (varchar (16), time 1, 20) Result: /* The time is generally the getdate () function or the field */CONVERT (varchar (10) in the data table, time 1, 23) Result: 2007-02

Use convert in SQL server2000 to obtain the datetime data type style (full)

DateDataFormatTwo examples:

CONVERT (varchar (16), time 1, 20) Result:/* The time is generally the getdate () function or the field in the data table */

CONVERT (varchar (10), time 1, 23) Result: 2007-02-01/* varchar (10) indicatesDateOutputFormat. If it is not long enough, it will be intercepted */

Statement and query result:
Select CONVERT (varchar (100), GETDATE (), 0): 05 16 2006 AM
Select CONVERT (varchar (100), GETDATE (), 1): 05/16/06
Select CONVERT (varchar (100), GETDATE (), 2): 06.05.16
Select CONVERT (varchar (100), GETDATE (), 3): 16/05/06
Select CONVERT (varchar (100), GETDATE (), 4): 16.05.06
Select CONVERT (varchar (100), GETDATE (), 5): 16-05-06
Select CONVERT (varchar (100), GETDATE (), 6): 16 05 06
Select CONVERT (varchar (100), GETDATE (), 7): 05 16, 06
Select CONVERT (varchar (100), GETDATE (), 8): 10:57:46
Select CONVERT (varchar (100), GETDATE (), 9): 05 16 2006 10: 57: 46: 827AM
Select CONVERT (varchar (100), GETDATE (), 10): 05-16-06
Select CONVERT (varchar (100), GETDATE (), 11): 06/05/16
Select CONVERT (varchar (100), GETDATE (), 12): 060516
Select CONVERT (varchar (100), GETDATE (), 13): 16 05 2006 10: 57: 46: 937
Select CONVERT (varchar (100), GETDATE (), 14): 10: 57: 46: 967
Select CONVERT (varchar (100), GETDATE (), 20): 10:57:47
Select CONVERT (varchar (100), GETDATE (), 21): 10:57:47. 157
Select CONVERT (varchar (100), GETDATE (), 22): 05/16/06 10:57:47 AM
Select CONVERT (varchar (100), GETDATE (), 23 ):
Select CONVERT (varchar (100), GETDATE (), 24): 10:57:47
Select CONVERT (varchar (100), GETDATE (), 25): 10:57:47. 250
Select CONVERT (varchar (100), GETDATE (), 100): 05 16 2006 AM
Select CONVERT (varchar (100), GETDATE (), 101): 05/16/2006
Select CONVERT (varchar (100), GETDATE (), 102): 2006.05.16
Select CONVERT (varchar (100), GETDATE (), 103): 16/05/2006
Select CONVERT (varchar (100), GETDATE (), 104): 16.05.2006
Select CONVERT (varchar (100), GETDATE (), 105): 16-05-2006
Select CONVERT (varchar (100), GETDATE (), 106): 16 05 2006
Select CONVERT (varchar (100), GETDATE (), 107): 05 16,200 6
Select CONVERT (varchar (100), GETDATE (), 108): 10:57:49
Select CONVERT (varchar (100), GETDATE (), 109): 05 16 2006 10: 57: 49: 437AM
Select CONVERT (varchar (100), GETDATE (), 110): 05-16-2006
Select CONVERT (varchar (100), GETDATE (), 111): 2006/05/16
Select CONVERT (varchar (100), GETDATE (), 112): 20060516
Select CONVERT (varchar (100), GETDATE (), 113): 16 05 2006 10: 57: 49: 513
Select CONVERT (varchar (100), GETDATE (), 114): 10: 57: 49: 547
Select CONVERT (varchar (100), GETDATE (), 120): 10:57:49
Select CONVERT (varchar (100), GETDATE (), 121): 10:57:49. 700
Select CONVERT (varchar (100), GETDATE (), 126): 2006-05-16T10: 57: 49.827
Select CONVERT (varchar (100), GETDATE (), 130): 18 ???? ?????? 1427 10: 57: 49: 907AM
Select CONVERT (varchar (100), GETDATE (), 131): 18/04/1427 10: 57: 49: 920AM

Note:
Use CONVERT:

CONVERT (data_type [(length)], expression [, style])

Parameters
Expression

Is it any valid Microsoft? SQL Server? Expression ..

Data_type

The data types provided by the target system, including bigint and SQL _variant. User-Defined data types cannot be used.
Length

Optional parameters of the nchar, nvarchar, char, varchar, binary, or varbinary data type.

Style

DateFormatStyle, to convert datetime or smalldatetime data to character data (nchar, nvarchar, char, varchar, nchar, or nvarchar data type); or stringFormatStyle to convert float, real, money, or smallmoney data to character data (nchar, nvarchar, char, varchar, nchar, or nvarchar data type ).

SQL Server supports data in the Arabic style using the Kuwait AlgorithmFormat.

In the table, the two columns on the left represent converting datetime or smalldatetime to the style value of the character data. Add 100 to the style value to obtain the four-digit year (yyyy) of the century ).

Without Century digital (yy) with Century digital (yyyy)
Standard
Input/Output **
-0 or 100 (*) Default Value: mon dd yyyy hh: miAM (or PM)
1 101 us mm/dd/yyyy
2 102 ANSI yy. mm. dd
3 103 UK/French dd/mm/yy
4 104 German dd. mm. yy
5 105 Italian dd-mm-yy
6 106-dd mon yy
7 107-mon dd, yy
8 108-hh: mm: ss
-9 or 109 (*) Default Value + millisecond mon dd yyyy hh: mi: ss: mmmAM (or PM)
10 110 US mm-dd-yy
11 111 yy/mm/dd in Japan
12 112 ISO yymmdd
-13 or 113 (*) European default value + millisecond dd mon yyyy hh: mm: ss: mmm (24 h)
14 114-hh: mi: ss: mmm (24 h)
-20 or 120 (*) ODBC specification yyyy-mm-dd hh: mm: ss [. fff]
-21 or 121 (*) ODBC specifications (in milliseconds) yyyy-mm-dd hh: mm: ss [. fff]
-126 (***) ISO8601 yyyy-mm-dd Thh: mm: ss. mmm (without spaces)
-130 * Hijri ***** dd mon yyyy hh: mi: ss: mmmAM
-131 * Hijri ***** dd/mm/yy hh: mi: ss: mmmAM

* The default value (style 0, 100, 9, 109, 13, 113, 20, 120, 21, or 121) always returns century digits (yyyy ).
** Input when converted to datetime; output when converted to character data.
* ** It is specially used for XML. For the conversion from datetime or smalldatetime to character data, the outputFormatAs shown in the table. For data conversion from float, money, smallmoney to character, the output is equivalent to style 2. For data conversion from real to character, the output is equivalent to style 1.
* *** Hijri is a calendar system with several forms of change. Microsoft? SQL Server? 2000 use the Kuwait algorithm.

?

Important by default, SQL Server interprets two-digit years based on the end year 2049. That is, the year 49 with two digits is interpreted as 2049, and the year 50 with two digits is interpreted as 1950. Many client applications (such as client applications based on OLE automation objects) Use 2030 as the end year. SQL Server provides a configuration option ("two-digit cutoff year") to change the end year used by SQL Server andDateFor consistency processing. However, the safest way is to specify a four-digit year.

When converting from smalldatetime to character data, the style that contains seconds or milliseconds will display zero at these locations. When converting from the datetime or smalldatetime value, you can use the appropriate char or varchar data type length to truncate unnecessaryDate.

?

To convert a stringDateIn the same way.
Select CONVERT (varchar, CONVERT (datetime, '11 23 2011? PM ', 0), 20)