sql,sql-server,database-design,best-fit
Three choices: Think ahead of time and try to foresee all posible fields needed and compile them in your table. Lets say we got a client's table which can be both people and corporations. We'd do something like this in the table: example: [Client] first_name /* person */ last_name /*...
After waiting for 2+ weeks for an answer to this question, I am assuming that my following guesses are the correct answer to this question. The need for this new archetype from 6.1 version is: 1. To avoid committing the auto generated services files by mistake to our version control...