If you have 2 tables that share the same PK and have few fields and most of the rows have values for all (or many fields), merging them could save you some space as for each table, each PK has to be stored in both tables. But I would avoid having "god tables" with too many fields.
But at the end again: It depends you model. Think thoroughly about it. 2016-10-26 10:17 GMT+02:00 Kant Kodali <k...@peernova.com>: > I guess the question can be rephrased into "What is the overhead of > creating and maintaining an additional table?" > > On Wed, Oct 26, 2016 at 1:12 AM, Ali Akhtar <ali.rac...@gmail.com> wrote: > >> Depends on the use case. No one right answer. >> >> On Wed, Oct 26, 2016 at 1:03 PM, Kant Kodali <k...@peernova.com> wrote: >> >>> If one were given a choice of fitting all the data into one table vs >>> fitting the data into two tables while say (keeping all the runtime and >>> space complexity for CRUD operations the same in either case) which one >>> would you choose and why? >>> >>> >> > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer
