Re: SQL Database design question
From: Erland Sommarskog <esquel_at_sommarskog.se>
Date: Mon, 7 Feb 2005 22:16:34 +0000 (UTC)
Message-ID: <Xns95F6EC826B9B1Yazorman_at_127.0.0.1>
>
> The problem with this is the case when a database is part of a software
> package that is sold to multiple clients.
>
> The DBA typically works for a client, while the original database
> designer works for the vendor, or the people the vendor bought the
> rights from. I think this is not a trivial distinction.
Date: Mon, 7 Feb 2005 22:16:34 +0000 (UTC)
Message-ID: <Xns95F6EC826B9B1Yazorman_at_127.0.0.1>
David Cressey (david.cressey_at_earthlink.net) writes:
> "William Cleveland" <WCleveland_at_Ameritech.Net> wrote in message
> news:a3CNd.1986$ng6.448_at_newssvr17.news.prodigy.com...
>
>> I'm afraid I don't have a good solution, except for the suggestion >> I've made at work that both the DBA *and* the original database >> designer sign off on changes in a database. So far, no luck.
>
> The problem with this is the case when a database is part of a software
> package that is sold to multiple clients.
>
> The DBA typically works for a client, while the original database
> designer works for the vendor, or the people the vendor bought the
> rights from. I think this is not a trivial distinction.
-- Erland Sommarskog, SQL Server MVP, esquel_at_sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinfo/productdoc/2000/books.aspReceived on Mon Feb 07 2005 - 23:16:34 CET