PARSE (Transact-SQL)

 

THIS TOPIC APPLIES TO:yesSQL Server (starting with 2008)yesAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

Returns the result of an expression, translated to the requested data type in SQL Server.

Topic link icon Transact-SQL Syntax Conventions

  
PARSE ( string_value AS data_type [ USING culture ] )  

string_value
nvarchar(4000) value representing the formatted value to parse into the specified data type.

string_value must be a valid representation of the requested data type, or PARSE raises an error.

data_type
Literal value representing the data type requested for the result.

culture
Optional string that identifies the culture in which string_value is formatted.

If the culture argument is not provided, then the language of the current session is used. This language is set either implicitly, or explicitly by using the SET LANGUAGE statement. culture accepts any culture supported by the .NET Framework; it is not limited to the languages explicitly supported by SQL Server. If the culture argument is not valid, PARSE raises an error.

Returns the result of the expression, translated to the requested data type.

Null values passed as arguments to PARSE are treated in two ways:

  1. If a null constant is passed, an error is raised. A null value cannot be parsed into a different data type in a culturally aware manner.

  2. If a parameter with a null value is passed at run time, then a null is returned, to avoid canceling the whole batch.

Use PARSE only for converting from string to date/time and number types. For general type conversions, continue to use CAST or CONVERT. Keep in mind that there is a certain performance overhead in parsing the string value.

PARSE relies on the presence of .the .NET Framework Common Language Runtime (CLR).

This function will not be remoted since it depends on the presence of the CLR. Remoting a function that requires the CLR would cause an error on the remote server.

More information about the data_type parameter

The values for the data_type parameter are restricted to the types shown in the following table, together with styles. The style information is provided to help determine what types of patterns are allowed. For more information on styles, see the .NET Framework documentation for the System.Globalization.NumberStyles and DateTimeStyles enumerations.

CategoryType.NET Framework typeStyles used
NumericbigintInt64NumberStyles.Number
NumericintInt32NumberStyles.Number
NumericsmallintInt16NumberStyles.Number
NumerictinyintByteNumberStyles.Number
NumericdecimalDecimalNumberStyles.Number
NumericnumericDecimalNumberStyles.Number
NumericfloatDoubleNumberStyles.Float
NumericrealSingleNumberStyles.Float
NumericsmallmoneyDecimalNumberStyles.Currency
NumericmoneyDecimalNumberStyles.Currency
Date and TimedateDateTimeDateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal
Date and TimetimeTimeSpanDateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal
Date and TimedatetimeDateTimeDateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal
Date and TimesmalldatetimeDateTimeDateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal
Date and Timedatetime2DateTimeDateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal
Date and TimedatetimeoffsetDateTimeOffsetDateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal

More information about the culture parameter

The following table shows the mappings from SQL Server languages to .NET Framework cultures.

Full nameAliasLCIDSpecific culture
us_englishEnglish1033en-US
DeutschGerman1031de-DE
FrançaisFrench1036fr-FR
日本語Japanese1041ja-JP
DanskDanish1030da-DK
EspañolSpanish3082es-ES
ItalianoItalian1040it-IT
NederlandsDutch1043nl-NL
NorskNorwegian2068nn-NO
PortuguêsPortuguese2070pt-PT
SuomiFinnish1035fi
SvenskaSwedish1053sv-SE
češtinaCzech1029Cs-CZ
magyarHungarian1038Hu-HU
polskiPolish1045Pl-PL
românăRomanian1048Ro-RO
hrvatskiCroatian1050hr-HR
slovenčinaSlovak1051Sk-SK
slovenskiSlovenian1060Sl-SI
ελληνικάGreek1032El-GR
българскиBulgarian1026bg-BG
русскийRussian1049Ru-RU
TürkçeTurkish1055Tr-TR
BritishBritish English2057en-GB
eestiEstonian1061Et-EE
latviešuLatvian1062lv-LV
lietuviųLithuanian1063lt-LT
Português (Brasil)Brazilian1046pt-BR
繁體中文Traditional Chinese1028zh-TW
한국어Korean1042Ko-KR
简体中文Simplified Chinese2052zh-CN
ArabicArabic1025ar-SA
ไทยThai1054Th-TH

A. PARSE into datetime2

SELECT PARSE('Monday, 13 December 2010' AS datetime2 USING 'en-US') AS Result;  

Here is the result set.

Result  
---------------  
2010-12-13 00:00:00.0000000  
  
(1 row(s) affected)  

B. PARSE with currency symbol

SELECT PARSE('€345,98' AS money USING 'de-DE') AS Result;  

Here is the result set.

Result  
---------------  
345.98  
  
(1 row(s) affected)  

C. PARSE with implicit setting of language

-- The English language is mapped to en-US specific culture  
SET LANGUAGE 'English';  
SELECT PARSE('12/16/2010' AS datetime2) AS Result;  

Here is the result set.

Result  
---------------  
2010-12-16 00:00:00.0000000  
  
(1 row(s) affected)  

Community Additions

ADD
Show: