date (Transact-SQL) - SQL Server (2024)

  • Article

Applies to: date (Transact-SQL) - SQL Server (1) SQL Server date (Transact-SQL) - SQL Server (2) Azure SQL Database date (Transact-SQL) - SQL Server (3) Azure SQL Managed Instance date (Transact-SQL) - SQL Server (4) Azure Synapse Analytics date (Transact-SQL) - SQL Server (5) Analytics Platform System (PDW) date (Transact-SQL) - SQL Server (6) SQL analytics endpoint in Microsoft Fabric date (Transact-SQL) - SQL Server (7) Warehouse in Microsoft Fabric

Defines a date in SQL Server. The date data type was introduced in SQL Server 2008 (10.0.x).

date description

PropertyValue
SyntaxDATE
UsageDECLARE @MyDate DATE

CREATE TABLE Table1 (Column1 DATE)

Default string literal format

(used for down-level client)

yyyy-MM-dd

For more information, see the Backward compatibility for down-level clients section.

Range0001-01-01 through 9999-12-31 (1582-10-15 through 9999-12-31 for Informatica)

January 1, 1 CE (Common Era) through December 31, 9999 CE (October 15, 1582 CE through December 31, 9999 CE for Informatica)

Element rangesyyyy is four digits from 0001 to 9999 that represent a year. Informatica limits yyyy to the range 1582 to 9999.

MM is two digits from 01 to 12 that represent a month in the specified year.

dd is two digits from 01 to 31, depending on the month, which represents a day of the specified month.

Character length10 positions
Precision, scale10, 0
Storage size3 bytes, fixed
Storage structureone 3-byte integer stores date
AccuracyOne day
Default value1900-01-01

This value is used for the appended date part for implicit conversion from time to datetime2 or datetimeoffset.

CalendarGregorian
User-defined fractional second precisionNo
Time zone offset aware and preservationNo
Daylight saving awareNo

Supported string literal formats for date

The following tables show the valid string literal formats for the date data type.

NumericDescription
mdy

[m]m/dd/[yy]yy

[m]m-dd-[yy]yy

[m]m.dd.[yy]yy

myd

mm/[yy]yy/dd

mm-[yy]yy/dd

[m]m.[yy]yy.dd

dmy

dd/[m]m/[yy]yy

dd-[m]m-[yy]yy

dd.[m]m.[yy]yy

dym

dd/[yy]yy/[m]m

dd-[yy]yy-[m]m

dd.[yy]yy.[m]m

ymd

[yy]yy/[m]m/dd

[yy]yy-[m]m-dd

[yy]yy-[m]m-dd

[m]m, dd, and [yy]yy represent month, day, and year in a string with slash marks (/), hyphens (-), or periods (.) as separators.

Only four-digit or two-digit years are supported. Use four-digit years whenever possible. To specify an integer from 0001 to 9999 that represents the cutoff year for interpreting two-digit years as four-digit years, use the Two digit year cutoff server configuration option.

Note: For Informatica, yyyy is limited to the range 1582 to 9999.

A two-digit year that is less than or equal to the last two digits of the cutoff year is in the same century as the cutoff year. A two-digit year greater than the last two digits of the cutoff year is in the century that comes before the cutoff year. For example, if the two-digit year cutoff is the default 2049, the two-digit year 49 is interpreted as 2049 and the two-digit year 50 is interpreted as 1950.

The current language setting determines the default date format. You can change the date format by using the SET LANGUAGE and SET DATEFORMAT statements.

The ydm format isn't supported for date.

AlphabeticalDescription
mon [dd][,] yyyy

mon dd[,] [yy]

mon yyyy [dd]

[dd] mon[,] yyyy

dd mon[,][yy]yy

dd [yy]yy mon

[dd] yyyy mon

yyyy mon [dd]

yyyy [dd] mon

mon represents the full month name, or the month abbreviation, given in the current language. Commas are optional and capitalization is ignored.

To avoid ambiguity, use four-digit years.

If the day is missing, the first day of the month is supplied.

ISO 8601Description
yyyy-MM-dd

yyyyMMdd

Same as the SQL standard. This format is the only format defined as an international standard.
UnseparatedDescription
[yy]yyMMdd

yyyy[MMdd]

The date data can be specified with four, six, or eight digits. A six-digit or eight-digit string is always interpreted as ymd. The month and day must always be two digits. A four-digit string is interpreted as the year.
ODBCDescription
{ d 'yyyy-MM-dd' }ODBC API specific.
W3C XML formatDescription
yyyy-MM-ddTZDSupported for XML/SOAP usage.

TZD is the time zone designator (Z or +hh:mm or -hh:mm):

- hh:mm represents the time zone offset. hh is two digits, ranging from 0 to 14, which represent the number of hours in the time zone offset.
- mm is two digits, ranging from 0 to 59, which represent the number of additional minutes in the time zone offset.
- + (plus) or - (minus) is the mandatory sign of the time zone offset. This sign indicates that, to obtain the local time, the time zone offset is added or subtracted from the Coordinated Universal Times (UTC) time. The valid range of time zone offset is from -14:00 to +14:00.

ANSI and ISO 8601 compliance

date complies with the ANSI SQL standard definition for the Gregorian calendar:

NOTE 85 - Datetime data types will allow dates in the Gregorian format to be stored in the date range 0001-01-01 CE through 9999-12-31 CE.

The default string literal format, which is used for down-level clients, complies with the SQL standard form that is defined as yyyy-MM-dd. This format is the same as the ISO 8601 definition for DATE.

Note

For Informatica, the range is limited to 1582-10-15 (October 15, 1582 CE) to 9999-12-31 (December 31, 9999 CE).

Backward compatibility for down-level clients

Some down-level clients don't support the time, date, datetime2, and datetimeoffset data types. The following table shows the type mapping between an up-level instance of SQL Server and down-level clients.

SQL Server data typeDefault string literal format passed to down-level clientDown-level ODBCDown-level OLEDBDown-level JDBCDown-level SQLCLIENT
timehh:mm:ss[.nnnnnnn]SQL_WVARCHAR or SQL_VARCHARDBTYPE_WSTR or DBTYPE_STRJava.sql.StringString or SqString
dateyyyy-MM-ddSQL_WVARCHAR or SQL_VARCHARDBTYPE_WSTR or DBTYPE_STRJava.sql.StringString or SqString
datetime2yyyy-MM-dd HH:mm:ss[.nnnnnnn]SQL_WVARCHAR or SQL_VARCHARDBTYPE_WSTR or DBTYPE_STRJava.sql.StringString or SqString
datetimeoffsetyyyy-MM-dd HH:mm:ss[.nnnnnnn] [+ or -]hh:mmSQL_WVARCHAR or SQL_VARCHARDBTYPE_WSTR or DBTYPE_STRJava.sql.StringString or SqString

Convert date and time data

When you convert to date and time data types, SQL Server rejects all values it doesn't recognize as dates or times. For information about using the CAST and CONVERT functions with date and time data, see CAST and CONVERT (Transact-SQL).

Convert date to other date and time types

This section describes what occurs when you convert a date data type to other date and time data types.

When the conversion is to time(n), the conversion fails, and error message 206 is raised:

Operand type clash: date is incompatible with time.

If the conversion is to datetime, the date component is copied. The following code shows the results of converting a date value to a datetime value.

DECLARE @date DATE = '12-10-25';DECLARE @datetime DATETIME = @date;SELECT @date AS '@date', @datetime AS '@datetime';

Here is the result set.

@date @datetime---------- -----------------------2025-12-10 2025-12-10 00:00:00.000

When the conversion is to smalldatetime, the date value is in the range of a smalldatetime, the date component is copied, and the time component is set to 00:00:00.000. When the date value is outside the range of a smalldatetime value, error message 242 is raised, and the smalldatetime value is set to NULL:

The conversion of a date data type to a smalldatetime data types resulted in an out-of-range value.

The following code shows the results of converting a date value to a smalldatetime value.

DECLARE @date DATE = '1912-10-25';DECLARE @smalldatetime SMALLDATETIME = @date;SELECT @date AS '@date', @smalldatetime AS '@smalldatetime';

Here is the result set.

@date @smalldatetime---------- -------------------1912-10-25 1912-10-25 00:00:00

For conversion to datetimeoffset(n), date is copied, and the time is set to 00:00.0000000 +00:00. The following code shows the results of converting a date value to a datetimeoffset(3) value.

DECLARE @date DATE = '1912-10-25';DECLARE @datetimeoffset DATETIMEOFFSET(3) = @date;SELECT @date AS '@date', @datetimeoffset AS '@datetimeoffset';

Here is the result set.

@date @datetimeoffset---------- ------------------------------1912-10-25 1912-10-25 00:00:00.000 +00:00

When the conversion is to datetime2(n), the date component is copied, and the time component is set to 00:00.000000. The following code shows the results of converting a date value to a datetime2(3) value.

DECLARE @date DATE = '1912-10-25'DECLARE @datetime2 DATETIME2(3) = @date;SELECT @date AS '@date', @datetime2 AS '@datetime2(3)';

Here is the result set.

@date @datetime2(3)---------- -----------------------1912-10-25 1912-10-25 00:00:00.000

Convert string literals to date

Conversions from string literals to date and time types are allowed if all parts of the strings are in valid formats. Otherwise, a runtime error is raised. Implicit conversions or explicit conversions that don't specify a style, from date and time types to string literals, are in the default format of the current session. The following table shows the rules for converting a string literal to the date data type.

Input string literaldate
ODBC DATEODBC string literals are mapped to the datetime data type. Any assignment operation from ODBC DATETIME literals into a date type causes an implicit conversion between datetime and the type that the conversion rules define.
ODBC TIMESee previous ODBC DATE rule.
ODBC DATETIMESee previous ODBC DATE rule.
DATE onlyTrivial
TIME onlyDefault values are supplied.
TIMEZONE onlyDefault values are supplied.
DATE + TIMEThe DATE part of the input string is used.
DATE + TIMEZONENot allowed.
TIME + TIMEZONEDefault values are supplied.
DATE + TIME + TIMEZONEThe DATE part of local DATETIME is used.

Examples

The following example compares the results of casting a string to each date and time data type.

SELECT CAST('2022-05-08 12:35:29.1234567 +12:15' AS TIME(7)) AS 'time', CAST('2022-05-08 12:35:29.1234567 +12:15' AS DATE) AS 'date', CAST('2022-05-08 12:35:29.123' AS SMALLDATETIME) AS 'smalldatetime', CAST('2022-05-08 12:35:29.123' AS DATETIME) AS 'datetime', CAST('2022-05-08 12:35:29.1234567 +12:15' AS DATETIME2(7)) AS 'datetime2', CAST('2022-05-08 12:35:29.1234567 +12:15' AS DATETIMEOFFSET(7)) AS 'datetimeoffset';

Here is the result set.

Data typeOutput
time12:35:29.1234567
date2022-05-08
smalldatetime2022-05-08 12:35:00
datetime2022-05-08 12:35:29.123
datetime22022-05-08 12:35:29.1234567
datetimeoffset2022-05-08 12:35:29.1234567 +12:15

See also

  • CAST and CONVERT (Transact-SQL)

SQL Server is a robust relational database management system developed by Microsoft. It includes various data types to manage and manipulate different kinds of data. The date data type, introduced in SQL Server 2008, offers specific properties, syntax, and functionalities tailored for handling date-related information within the database.

The date data type within SQL Server facilitates the storage and manipulation of date values. It's defined with specific characteristics, including:

Properties:

  • Syntax: DATE
  • Usage:
    • Declaration: DECLARE @MyDate DATE
    • Table Creation: CREATE TABLE Table1 (Column1 DATE)
  • Default String Literal Format (for down-level clients): yyyy-MM-dd
  • Range: From January 1, 1 CE (Common Era) through December 31, 9999 CE (1582-10-15 through 9999-12-31 for Informatica)
  • Element Ranges: yyyy (year), MM (month), dd (day)
  • Character Length: 10 positions
  • Precision, Scale: 10, 0
  • Storage Size: 3 bytes (fixed)
  • Storage Structure: One 3-byte integer stores the date
  • Accuracy: Accurate to a day
  • Default Value: 1900-01-01

Supported String Literal Formats for Date:

SQL Server supports various string literal formats for dates, allowing flexibility in how dates can be represented and interpreted. Some of these formats include:

  • Numeric descriptions like yyyymmdd or mm/dd/yyyy
  • Alphabetic descriptions such as mon yyyy or yyyy mon
  • ISO 8601 format (yyyy-MM-dd or yyyyMMdd)
  • Unseparated formats (yyMMdd or yyyyMMdd)
  • ODBC and W3C XML formats

Conversion and Compatibility:

SQL Server provides conversion options between date types and other related data types, like datetime, smalldatetime, datetime2, and datetimeoffset. It also covers conversions from string literals to date types and vice versa, ensuring compatibility and data integrity within the database.

Additionally, SQL Server supports setting the date format based on the current language settings, allowing users to adjust how dates are displayed and interpreted within the system.

The article you provided seems to comprehensively cover the date data type in SQL Server, detailing its syntax, supported formats, conversion rules, and compatibility considerations. If you have any specific queries or need further details on a particular aspect, feel free to ask!

date (Transact-SQL) - SQL Server (2024)
Top Articles
Latest Posts
Article information

Author: Manual Maggio

Last Updated:

Views: 6504

Rating: 4.9 / 5 (69 voted)

Reviews: 84% of readers found this page helpful

Author information

Name: Manual Maggio

Birthday: 1998-01-20

Address: 359 Kelvin Stream, Lake Eldonview, MT 33517-1242

Phone: +577037762465

Job: Product Hospitality Supervisor

Hobby: Gardening, Web surfing, Video gaming, Amateur radio, Flag Football, Reading, Table tennis

Introduction: My name is Manual Maggio, I am a thankful, tender, adventurous, delightful, fantastic, proud, graceful person who loves writing and wants to share my knowledge and understanding with you.