>No, char still has its place, wherever you need to store fixed size strings (let's say the SIN, 9 chars) or mostly the same size (let's say car license plates, 6 or 7 characters) (I know my examples are very short), if you use varchar for this examples, you are actually paying an overhead of 2 bytes per record, that is the space reserved by SQL to store the length of the actual string.

Thanks, I still see that some of our fields will need to be updated, as far as the data type goes, for space allocation optimization.