- SQL Tutorial
- SQL - Home
- SQL - Overview
- SQL - RDBMS Concepts
- SQL - Databases
- SQL - Syntax
- SQL - Data Types
- SQL - Operators
- SQL - Expressions
- SQL Database
- SQL - Create Database
- SQL - Drop Database
- SQL - Select Database
- SQL - Rename Database
- SQL - Show Databases
- SQL - Backup Database
- SQL Table
- SQL - Create Table
- SQL - Show Tables
- SQL - Rename Table
- SQL - Truncate Table
- SQL - Clone Tables
- SQL - Temporary Tables
- SQL - Alter Tables
- SQL - Drop Table
- SQL - Delete Table
- SQL - Constraints
- SQL Queries
- SQL - Insert Query
- SQL - Select Query
- SQL - Select Into
- SQL - Insert Into Select
- SQL - Update Query
- SQL - Delete Query
- SQL - Sorting Results
- SQL Views
- SQL - Create Views
- SQL - Update Views
- SQL - Drop Views
- SQL - Rename Views
- SQL Operators and Clauses
- SQL - Where Clause
- SQL - Top Clause
- SQL - Distinct Clause
- SQL - Order By Clause
- SQL - Group By Clause
- SQL - Having Clause
- SQL - AND & OR
- SQL - BOOLEAN (BIT) Operator
- SQL - LIKE Operator
- SQL - IN Operator
- SQL - ANY, ALL Operators
- SQL - EXISTS Operator
- SQL - CASE
- SQL - NOT Operator
- SQL - NOT EQUAL
- SQL - IS NULL
- SQL - IS NOT NULL
- SQL - NOT NULL
- SQL - BETWEEN Operator
- SQL - UNION Operator
- SQL - UNION vs UNION ALL
- SQL - INTERSECT Operator
- SQL - EXCEPT Operator
- SQL - Aliases
- SQL Joins
- SQL - Using Joins
- SQL - Inner Join
- SQL - Left Join
- SQL - Right Join
- SQL - Cross Join
- SQL - Full Join
- SQL - Self Join
- SQL - Delete Join
- SQL - Update Join
- SQL - Left Join vs Right Join
- SQL - Union vs Join
- SQL Keys
- SQL - Unique Key
- SQL - Primary Key
- SQL - Foreign Key
- SQL - Composite Key
- SQL - Alternate Key
- SQL Indexes
- SQL - Indexes
- SQL - Create Index
- SQL - Drop Index
- SQL - Show Indexes
- SQL - Unique Index
- SQL - Clustered Index
- SQL - Non-Clustered Index
- Advanced SQL
- SQL - Wildcards
- SQL - Comments
- SQL - Injection
- SQL - Hosting
- SQL - Min & Max
- SQL - Null Functions
- SQL - Check Constraint
- SQL - Default Constraint
- SQL - Stored Procedures
- SQL - NULL Values
- SQL - Transactions
- SQL - Sub Queries
- SQL - Handling Duplicates
- SQL - Using Sequences
- SQL - Auto Increment
- SQL - Date & Time
- SQL - Cursors
- SQL - Common Table Expression
- SQL - Group By vs Order By
- SQL - IN vs EXISTS
- SQL - Database Tuning
- SQL Function Reference
- SQL - Date Functions
- SQL - String Functions
- SQL - Aggregate Functions
- SQL - Numeric Functions
- SQL - Text & Image Functions
- SQL - Statistical Functions
- SQL - Logical Functions
- SQL - Cursor Functions
- SQL - JSON Functions
- SQL - Conversion Functions
- SQL - Datatype Functions
- SQL Useful Resources
- SQL - Questions and Answers
- SQL - Quick Guide
- SQL - Useful Functions
- SQL - Useful Resources
- SQL - Discussion
SQL - TRY_CONVERT() Function
The SQL TRY_CONVERT() function tries to change the datatype of an expression. In case of unsuccessful conversion, the function will return NULL. If not, it will give you the converted value.
The only difference between the TRY_CONVERT() and CONVERT() functions is when the conversion is failed. CONVERT() throws an error whereas TRY CONVERT() returns a NULL.
Syntax
Following is the syntax of the SQL TRY_CAST() function −
TRY_CONVERT ( data_type [ ( length ) ], expression [, style ] )
Parameters
This function accepts only four parameter. The same is described below −
expression − the valid expression that to be convert to data type.
datatype − It is the datatype that we want to convert the expression to.
length − It was used to define the length of any targeted data type, as it was an optional parameter of an integer type. the default value is 30.
style − It was the optional integer expression and specifies how TRY_CONVERT() function translates the given expression
Example
Let us try to convert the string to decimal with TRY_CONVERT() function by using the following query −
SELECT TRY_CONVERT(DECIMAL(6,2), '1234.5') AS Result;
Output
When we execute the above query, the output is obtained as follows −
+------------------------------------+ | Result| +------------------------------------+ | 1234.50 | +------------------------------------+
Example
Let's try to convert the string of valid date to datetime2 type by using the following query −
SELECT TRY_CONVERT (datetime2, '2023-02-23') AS Result;
Output
On executing the above query, the output is displayed as follows −
+------------------------------------+ | Result| +------------------------------------+ | 2023-02-23 00:00:00.0000000| +------------------------------------+
Example
Considering the following example, where we are going to convert the string to decimal, It will return NULL as it was unable to convert the string 1234.45 to decimal (3, 2). Let's check by using the below query −
SELECT TRY_CONVERT(decimal(3,2), '1234.45') AS Result;
Output
On executing the above query, the output is displayed as follows −
+------------------------------------+ | Result| +------------------------------------+ | NULL | +------------------------------------+
Example
Let's look into the following example, where we are using the style parameter to specify how the expression is translated and running the below queries −
SET LANGUAGE British; SELECT TRY_CONVERT(date, '02/23/2023', 101) AS "US", TRY_CONVERT(date, '20230223', 112) AS "ISO", TRY_CONVERT(date, '02/23/23', 1) AS "US (short)";
Output
The output for the above query is produced as given below −
+-------------------+----------------+---------------+ | US | ISO | US(short) | +-------------------+----------------+---------------+ | 2023-02-23 | 2023-02-23 | 2023-02-23 | +-------------------+----------------+---------------+
Example
Look at the following example, where we are going to convert the expression to the varchar and mentioning the style by using the following query −
SELECT TRY_CONVERT(varchar, '2023-02-23', 101) AS Result;
Output
If we compile and run the above query, the result is produced as follows −
+------------------------------------+ | Result| +------------------------------------+ | 2023-02-23 | +------------------------------------+
Example
let's look into the following example, where TRY_CONVERT() function return an error when the conversion is explicitly not permitted using the following query −
SELECT TRY_CONVERT(xml, 2) AS Result;
Output
On executing the above query, it will generate the following output as shown below −
Explicit conversion from data type int to xml is not allowed.
Example
Letâs consider another example, where we are going to use the TRY_CONVERT()function with case and running the following query −
SELECT CASE WHEN TRY_CAST('TUTORIALSPOINT' AS int) IS NOT NULL THEN 'CastFailed' ELSE 'CastSucceeded' END AS Result;
Output
When the query gets executed, it will generate the output as shown below −
+------------------------------------+ | Result| +------------------------------------+ | CastSucceeded | +------------------------------------+
Example
Considering the following example, where we are converting the expression to an int, which makes the value get truncated by using the following query −
SELECT TRY_CONVERT(int, 12.34) AS Result;
Output
When we execute the above query, the output is obtained as follows −
+------------------------------------+ | Result| +------------------------------------+ | 12 | +------------------------------------+