Posted by Tony Rogerson on 08/27/07 12:32

> That's funny -- here in sunny Austin I get the right answer with my
> connection settings. Moral to the story "Think globally (i.e. ISO)
> and act locally (i.e fix your dialect and proprietary setting)" to
> paraphrase the Greens.

I see, with YOUR regional settings it works - well that explains it all.

The rest of the planet should adopt Texas Regional settings I guess then.

Perhaps you should alter your statement about regional settings and people
letting the client sort it out then...

This issue is a good marker as to just how professional you really are; now
you know that use the date format YYYY-MM-DD cannot be trusted in SQL
Server, will you keep preaching the use of it?

Or will you use the ISO compliant YYYY-MM-DDT00:00:00 or YYYYMMDD instead?

I look forward to seeing that over the coming months.

--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]

• Next in forum: Problem Connect to Reporting Services via Mgmt Studio
• Prev in forum: Re: Convert CHAR YYYYMMDD to mm/dd/yyyy
• Thread view: Re: Convert CHAR YYYYMMDD to mm/dd/yyyy

[Reply to this message]