I also believe (though I'm happy to be corrected if I'm wrong) that you can later safely switch from a varchar to an nvarchar. You'd be in danger of truncating data if you went from nvarchar to varchar, but since varchar is a subset of nvarchar, changing the data type at a later date should be safe.
Judah On Thu, Feb 18, 2010 at 11:04 AM, Alan Rother <alan.rot...@gmail.com> wrote: > >>>>Just out of curiosity, when should I use nvarchar as opposed to varchar? > > nvarchar allows for an expanded set of characters, for example if you want > your app to be able to handle double byte characters for non latin languages > such as Chinese or Russian you would use nvarchar or ntext. > > However, nvarchar does require more space to store that data, so if you are > 100% certain you will NEVER need to accommodate double byte characters, then > varchar will work just fine. > > > =] > > > -- > Alan Rother > Adobe Certified Advanced ColdFusion MX 7 Developer > Manager, Phoenix Cold Fusion User Group, AZCFUG.org > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330886 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
