>>Hmmm, something to think about, for sure. And Sergey did already mention the performance degradation with updates. The table in question will not have heavy updates, except initially when the user is setting up their data (it's a codes table), so I think that performance-wise, we'll be ok using the varchars in this case. But, I'll definitely take this into consideration for other tables that I design. Thanks!
>>
>>~~Bonnie
>>
>No problemo. Unfortunately I've seen too many DB's where varchars were used way too much - down to varchar(1)!

Hi Daniel,

theoretically all true, but someone has made some benchmark with regard to?
And the log file ?

All this regards the mdf data file,
but what it is perceived to applicativo level is the time in order to write on the ldf log files,
and therefore I doubt that update a varchar it is less efficient than a char.

Fabio