Posted by Erland Sommarskog on 02/11/06 19:53

Gert-Jan Strik (sorry@toomuchspamalready.nl) writes:
> But I would probably also specify the datetime as '2006-02-07 02:07:00'.
> I still use SQL 7.0, and this format is upwards compatible. The format
> '2006-02-07T02:07:00' is harder to read, and needs at least SQL Server
> 2000.

But '2006-02-07 02:07:00' is subject to different interpretations depending
on dateformat settings. For instance try:

SET LANGUAGE Dutch
go
SELECT convert(datetime , '2006-02-07 02:07:00')
go
SET LANGUAGE Swedish
go
SELECT convert(datetime , '2006-02-07 02:07:00')
go

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Why the log file is growing too much upon running nested stored procedures (MS SQL 2K)
• Prev in forum: Resolving duplicates entries in table among 10 databases
• Thread view: Re: one for the SQL experts - dare I say TRICKY SQL!

[Reply to this message]