New answers tagged best-practices
At what normalisation stage is it recommend to split say Customers and Employees into a people table and then link to the unique attributes of Customers and Employees. The short answer here is none. Normalization, more formally called Projection-Join Normalization, is a scientific process in which one can remove redundancies in R-tables due ...
There could be several reason they continue to use an older version. It may be they've run into issues with newer versions and know to stay away from them. It could also be that they know the version they're on and can be much more efficient working in it which translates in to dollars. I see later versions lost support for sharding and had an overhaul to ...
Reverting to a valid backup is the most common and safest approach. You can reduce risk and likelihood of needing to restore from backup by versioning the changes. For instance, say your upgrade process involves 50 steps that have some sequence/order requirements. Any step or small group of steps that can survive a reboot after they are applied should ...
If the address is a single attribute there's nothing to be gained from moving out to another table. You're not suffering from a low normal form here, since there's no functional dependency from a non key attribute to the address. Things might be different if, say, you were storing the address as a set of attributes.
Top 50 recent answers are included