Re: Data modeling for a multi-company product
From: DBMS_Plumber <paul_geoffrey_brown_at_yahoo.com>
Date: 24 Jan 2007 13:22:05 -0800
Message-ID: <1169673725.670339.130780_at_m58g2000cwm.googlegroups.com>
> software for multiple companies to deploy, with a business requirement
> to ensure that you not be locked into a single OS or DBMS would be
> what?
Date: 24 Jan 2007 13:22:05 -0800
Message-ID: <1169673725.670339.130780_at_m58g2000cwm.googlegroups.com>
On Jan 24, 12:57 pm, "dawn" <dawnwolth..._at_gmail.com> wrote:
>So what you would do differently if you ran software company writing
> software for multiple companies to deploy, with a business requirement
> to ensure that you not be locked into a single OS or DBMS would be
> what?
Quit.
> And for the original question, if, additionally, you needed to be
> competitive by providing features such as the ability for each customer
> site to identify which attributes would be required for data entry for
> each such data collection mechanism (e.g. screen) would you design
> nullable attributes into your logical data model? Thanks for any clues
> on either question. --dawn
- Do the domains correctly. That solves 80% of the need for an 'out of bound' value.
- Modify the schema. For better or for worse, SQL applications don't start with INSERT and SELECT. They start with CREATE TABLE.