CHAR(64) or BINARY(32) To Store SHA256 Hash in SQL SERVER
I am debating which datatype to use when storing a SHA256 hash in SQL
Server. Should it be CHAR(64) or BINARY(32) ... The column will be part of
a unique clustered index. I know that I'm probably splitting hairs at this
point, however I want to do this right the first time and I know that at
times primitive data types are faster and other times the newer more
exotic types perform better. ( yes I know char(64) isn't all that new, but
it's newer than byte storage )
I've looked around and can't find anything about the performance of one
vs. the other in terms of search, etc.
No comments:
Post a Comment