NVARCHAR versus VARCHAR

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Archive: Backup and Recovery Synchronize databases on two separate active servers Back up tables from SQL Server 2005 database to a file Restore SQL Server 2000 backups in SQL Server 2005 Restoring a SQL Server database with a corrupt data file SQL Server error message: "Server out of memory" Configure log shipping between SQL Server 2000 and 2005 Restoring from msdb with only .mdf and .ldf files Extended stored procedure to back up databases Change tempdb from 'C' drive Back up stored procedure only

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

SQL Server provides both datatypes to store character information. For the most part the two datatypes are identical in how you would work with them within SQL Server or from an application. The difference is that nvarchar is used to store unicode data, which is used to store multilingual data in your database tables. Other languages have an extended set of character codes that need to be saved and this datatype allows for this extension. If your database will not be storing multilingual data you should use the varchar datatype instead. The reason for this is that nvarchar takes twice as much space as varchar, this is because of the need to store the extended character codes for other languages.

For news, advice and other information about SQL server development, click here.