>> I have a number of "clients" which re****t with a string
"client_id,client_model,0001001001", when the third part is a binary
string containing client's status. Each client model can have
various status message length and interpretation. For each of the
locations in the status message, stands it's description and it's
"im****tance level". <<
This is a **very** denormalized design. That is about all we can say
without more specs. You have what I call an "Automobiles, Squids and
Britney Spears" design -- many unrelated things forced into a single
structure that mixes data and metadata together, inviolation of any
kindof Normal Form. You should handle parsing this mess in the front
end before it gets to the database. Oh, are these binary strings high-
end or low-end, etc.? Then insert the data into normalized tables.
|
