I\'ve got 2 servers running SQL Server 2008, and I have the following query:
SELECT cast(\'13/1/2011\' as datetime)
If I execute this query
It is the language setting of the login
that controls how these ambiguous date formats are interpreted (though this can be overridden with an explicit SET DATEFORMAT
statement).
The DEFAULT_LANGUAGE
can be changed via ALTER LOGIN
Even better, don't rely on the SET DATEFORMAT
or DEFAULT_LANGUAGE
settings to ensure your date conversions work as expected. In SQL Server one should always—as a matter of best practice—either use a neutral format, or use an explicit format specifier, no matter what language settings are in use or what your dates look like. Try the following on both servers and you will have no problem.
Convert(datetime, '20110113')
Convert(datetime, '2011-01-13T00:00:00')
Convert(datetime, '13/1/2011', 103)
- see SQL Server Books Online: Cast and Convert for details.