special characters in the database

  • Hi

    What is the consequences/problems of using special characters eg  / in the SQL Server 2005 Database??especially for primary key field data??

    Appreciating

    rgds

    noneK

  • If you are referring special characters such as universal code(unicode), then you will have to use nvarchar, or nchar which take twice the disk space as usual characters, non-unicode.

    I am sure sorting will not be that faster using clustered indexes too and might have too many acans on your execution plans

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply