I could have converted it to another date/time value such as datetime or datetime2. It didn’t necessarily have to be the actual date type that I converted to. In this example we provided a string literal, whereas in the first example we explicitly converted the int to a char(8) string. That’s because SQL Server allows us to convert the string to a date. In this case it successfully converted the value to a date. SQL Server tells us that the conversion is not allowed.īut here’s what happens when we pass the number as a string literal: SELECT CAST( '20281030' AS date ) Result: Msg 529, Level 16, State 2, Line 1Įxplicit conversion from data type int to date is not allowed. Here’s an example of what happens when we try to directly convert the int to a date: SELECT CAST( 20281030 AS date ) But it does allow us to convert an int to a string, and then that string to the date type. The reason for this is because SQL Server doesn’t allow an explicit conversion from the int type to the date type. In this case I used CAST() to convert the number to a char(8), then I used another CAST() to convert that char(8) to a date.
Here’s an example to demonstrate: SELECT CAST( CAST( 20281030 AS char(8)) AS date ) This will enable us to perform date operations against it that we might not be able to do when it’s still in numeric form. When working with SQL Server, if we’re given a number that represents a date in the yyyymmdd format, we can use functions like CAST() or CONVERT() to convert that number to a valid date type.
0 kommentar(er)
