Writing International Transact-SQL Statements

Databases and database applications that use Transact-SQL statements will become more portable from one language to another, or will support multiple languages, if the following guidelines are followed:

• Replace all uses of the char, varchar, and text data types with nchar, nvarchar, and nvarchar(max). By doing this, you do not have to consider code page conversion issues. For more information, see Working with Unicode Data and Server-Side Programming with Unicode.
• When you perform month and day-of-week comparisons and operations, use the numeric date parts instead of the name strings. Different language settings return different names for the months and weekdays. For example, DATENAME(MONTH,GETDATE()) returns May when the language is set to U.S. English, returns Mai when the language is set to German, and returns mai when the language is set to French. Instead, use a function such as DATEPART that uses the number of the month instead of the name. Use the DATEPART names when you build result sets to be displayed to a user, because the date names are frequently more meaningful than a numeric representation. However, do not code any logic that depends on the displayed names being from a specific language.
• When you specify dates in comparisons or for input to INSERT or UPDATE statements, use constants that are interpreted the same way for all language settings:

  • ADO, OLE DB, and ODBC applications should use the ODBC timestamp, date, and time escape clauses of:
    { ts'yyyy-mm-ddhh**:mm:ss[.fff] '} such as: { ts'1998-09-24 10:02:20' }**
    { d'yyyy-mm-dd**'}** such as: { d'1998-09-24**'}**
    { t'hh:mm:ss'} such as: { t'10:02:20'}

  • Applications that use other APIs, or Transact-SQL scripts, stored procedures, and triggers, should use the unseparated numeric strings. For example, yyyymmdd as 19980924.

  • Applications that use other APIs, or Transact-SQL scripts, stored procedures, and triggers should use the CONVERT statement with an explicit style parameter for all conversions between the date and smalldate data types and character string data types. For example, the following statement is interpreted in the same way for all language or date format connection settings:

    SELECT *
    FROM AdventureWorks.Sales.SalesOrderHeader
    WHERE OrderDate = CONVERT(DATETIME, '19960719', 101)
    

    For more information, see CAST and CONVERT (Transact-SQL).

See Also

Other Resources

International Considerations for Databases and Database Engine Applications

Help and Information

Getting SQL Server 2005 Assistance

Change History

Release	History
17 July 2006	Changed content: Replaced the reference to ntext data type with nvarchar(max) data type.