<div>
I found this link and use this as one of our guidelines for best practices: <a href="http://msdn.microsoft.com/en-us/library/ms191307.aspx" rel="ugc">http://msdn.microsoft.com/en-us/library/ms191307.aspx</a><br />

</div>


<div>
The best way to handle the date storage in SQL is YYYY-MM-DD this will work in any region.<br />
<br />
When you want to display the date to users in their preferred format then the convert function is fine, you can do French/British with 103 I think.
</div>


<div>
Scott, <br />
thanks for that post. One thing I want to mention is we have completed our product for US , now we have to make chagnes so that it accommodates other languages and we want to maintain one standard code base. The approach you suggested is great, but we have to now make changes to all the table structures , there are so many tables. Any other suggestions ? How about writing a common function and using it globally , now we just have to replace the stored procedure with this function ? <br />
<br />

</div>


<div>
Sorry, forgot about the follow up qs!<br />
<br />
My personal perference would be to avoid a function unless absolutely needed, because of the overhead of functions.<br />
<br />
I would consider other alternatives instead. &nbsp;For example, instead of referring directly to any original table names, create a view(s) that pull from the original table. &nbsp;If really necessary, functions can be included in the views. &nbsp;That still isolates them from anyone writing SQL. &nbsp;IMO, you want the hand-written SQL to be independent of any need to know about always using specific functions on columns, etc..
</div>


<div>
<div class="content wysiwyg-content">
what is the best practicse to handle date in sql server for internationalization purpose ? Right now we store <br />
it as date/time field. When we extract it , we use the convert function - CONVERT(varchar(20),test_d<wbr />ate, 101 )<br />
to convert it back to the US format. How can we internationlize this with best practices ? Say eg in UK <br />
where it is dd/mm/yyyy. &nbsp;<br />
<br />
Should we write a common function or is there any way to override the existing convert function of sql server &nbsp;so that we need not make changes to all the stored procedures (is this recommended)? <br />
<br />
<br />

</div>
</div>


what is the best practicse to handle date in sql server for internationalization purpose ? Right now we store 
it as date/time field. When we extract it , we use the convert function - CONVERT(varchar(20),test_date, 101 )
to convert it back to the US format. How can we internationlize this with best practices ? Say eg in UK 
where it is dd/mm/yyyy.  

Should we write a common function or is there any way to override the existing convert function of sql server  so that we need not make changes to all the stored procedures (is this recommended)? 




best practices for Sql Server Internationalization to retrieve date ?

Oracle is an object-relational database management system. It supports a large number of languages and application development frameworks. Its primary languages are SQL, PL/SQL and Java, but it also includes support for C and C++. Oracle also has its own enterprise modules and application server software.

Oracle Database

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.

Microsoft SQL Server 2005

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.