Design database schemas around a common subset of objects

2021-11-07 Thread Erik Wienhold
I'm brainstorming ideas on how to design database schemas that share a common subset of objects and stumbled on some issues. Maybe someone has experience with such a design. Any ideas are welcome! Use case: My team wants a "template" database from which we can create databases for new customer

Re: Design database schemas around a common subset of objects

2021-11-07 Thread Adrian Klaver
On 11/6/21 17:02, Erik Wienhold wrote: I'm brainstorming ideas on how to design database schemas that share a common subset of objects and stumbled on some issues. Maybe someone has experience with such a design. Any ideas are welcome! Because of this issue I'm hesitant going with an exte

Re: Design database schemas around a common subset of objects

2021-11-07 Thread Erik Wienhold
Hi Adrian, > On 07/11/2021 18:38 Adrian Klaver wrote: > > My questions for this are: > > 1) How stable are the core objects? Hard to tell. A lot of changes were necessary for the prototype, as expected. It's considered stable by some team members, who unfortunately lack experience in database

Re: Design database schemas around a common subset of objects

2021-11-07 Thread Rich Shepard
On Mon, 8 Nov 2021, Erik Wienhold wrote: One thing I already know that may differ is how modelled objects are named in the real world. We deal with plots of land, hence the geographic data. Depending on the region, these plots may use different naming schemes relevant to legal documents. The c

Re: Design database schemas around a common subset of objects

2021-11-07 Thread Rob Sargent
> On Nov 7, 2021, at 6:10 PM, Rich Shepard for people are a natural key as is the > VIN (vehicle identification number) for ... vehicles. > > Rich Be very careful with SSN. Not as unique as you might think. As well as a stretch to call natural. > >