Re: mm/dd/yyyy format question



Joergen,

This is a VB.Net newsgroup not an SQL language newsgroup.

Why would you do that for an SQLSever which notate its dateTime in ticks and
for what has .Net very automatic localized methods?

To explain you more.
ISO8601 is used in Asia (not all countries)
dd-mm-yyyy is used in Europe/Africa/Australia/America with the exception of
USA and Mexico
mm-dd-yyyy is used in the USA and Mexico (from the last I am not even sure)

However with Net there is no need to think about that when you use the
settings of the OS (that is by doing nothing extra)

(If you use direct SQLServer without Net than you have to make a choose,
however that is not the situation).

In cases beside Net my preference is ISO8601 by the way.

Cor

"Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAM> schreef in bericht
news:fnriq11ul3hm1vht5mqdbhhasbkjaf92ci@xxxxxxxxxx
> On Tue, 20 Dec 2005 13:47:02 -0800, Roy
> <Roy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>Hi all,
>>
>>I'm creating a project that should always use this date format when
>>displays
>>the dates or create dates. The back end database is a SQL Server and I
>>like
>>to know what is the logical way to configure server, sql server or program
>>so
>>it always deals with date as mm/dd/yyyy format.
>>Thanks in advance.
>>
>>Roy
>
> Use the ISO 8601 format when passing date information as a string to
> SQL server, i.e. "YYYYMMDD".
>
>
> For more information, see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;173907
>
> Another interesting article about SQL Server date handling:
> http://www.sqljunkies.com/Article/6676BEAE-1967-402D-9578-9A1C7FD826E5.scuk
>
> More info about ISO 8601:
> http://www.cl.cam.ac.uk/~mgk25/iso-time.html
>
> As another poster replied, you should not presume that the
> system is configured to handle dates formatted in any
> particular manner. Specific (localized) formats should be reserved for
> input validation and output representation.
>
> Hope any of this helps.
>
> Regards,
>
> Joergen Bech
>
>
>


.



Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)

Loading