August 18, 2015 at 2:44 am
Hi all
I've got a couple of questions on collations and (unfortunately) Google doesn't have the answer to these.
We're setting up a new server and having a big discussion around collations and which one would be the best to use.
I'm leaning towards case sensitive (we've got some imported data that's case sensitive so codes like RX99Y and rx99y would mean two completely different things). I'm also leaning that way as I think it would force people to type the field names correctly and improve the coding standards (that could just be me being picky).
Others are leaning towards case insensitive and using another method to differentiate between the codes (e.g. making just that field case sensitive, converting to varbinary, etc.). They are also looking at using the COLLATE statement in the code but I think that would introduce a performance hit.
Anyone any thoughts?
August 18, 2015 at 6:24 am
In my opinion, you should choose the datatype to match the constraints of the data. So you put date in a (small)datetime column not char(x), numbers in a column for numbers - not char (y) and so on.
So, if your data dictates that case sensitivity is a concern, then your database should be case sensitive.
Just my opinion - others may disagree
-------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
I would never join a club that would allow me as a member - Groucho Marx
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply